What this category of data looks like
Yield rate and market data in the advertising marketing sector primarily comes from advertising campaign management backend APIs and third-party ad monitoring APIs. Data updates occur once daily at midnight, completing full settlement of the previous day’s data and generating that day’s daily report file. The data is in structured format, including fields such as ad plan ID, delivery time slot, impressions, clicks, conversions, cost per acquisition, total delivery cost, and total revenue. The corresponding units for each field are times, times, units, yuan, yuan, yuan respectively.
What constraints these characteristics impose on the tool calling and plugins workflow
Data is updated only once per day, so tool calling must be configured with a daily scheduled trigger mechanism, and frequent real-time requests should be avoided. The data fields include multi-dimensional delivery metrics and financial metrics, so tool calling must explicitly specify the fields to extract to avoid returning redundant data. The fields include a unique identifier for ad plans, so tool calling must pass valid plan ID parameters; otherwise, the corresponding data cannot be located. Some ad plans may have no conversions or no revenue, so tool calling must be configured with null value handling logic to avoid parsing failures.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
tool_call_schedule | 0 0 1 * * ? | Matches the daily midnight update rhythm of daily report data, ensuring access to the latest settled data |
tool_extract_fields | ["ad_plan_id","exposure","click","conversion","cost_per_acquisition","total_cost","total_revenue"] | Covers core metrics of advertising marketing daily reports, avoiding returning unnecessary fields |
request_timeout | 30 seconds | Adapts to the typical response duration of ad monitoring APIs, preventing call failures due to API delays |
null_value_policy | skip_empty_fields | Handles ad plan data with no conversions or revenue, avoiding parsing errors |
plan_id_filter | ["active_plans_only"] | Only pulls data for currently valid ad plans, reducing the volume of invalid data |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis, and testing on the target deployment’s own samples is recommended before finalizing settings.
Three common mistakes
- Symptom: A "The tool call is not supported" prompt appears in the interface, and the tool calling feature cannot be enabled. Cause: The tool calling switch was not enabled in the application settings, or the currently bound model does not have tool calling capabilities enabled.
- Symptom: The returned advertising data fields are missing, or the revenue and cost fields for some plans are empty. Cause: The value range for
tool_extract_fieldswas not specified correctly, or the null value handling policy was not configured. - Symptom: Calls to locally deployed models fail after version 4.8.19, with configurations identical to the older version. Cause: This version adjusted the parameter validation rules for plugin calls with local models, and the API port or authentication key for the local model was not updated synchronously.
How to confirm the configuration is complete
- Manually trigger a tool call, and check if the returned structured data includes all fields listed in the configured
tool_extract_fields. - View the application's tool calling logs to confirm that the daily scheduled trigger call requests were successfully initiated and valid data was obtained.
- Pass a known valid ad plan ID, and verify that the returned data matches the corresponding metrics displayed in the ad delivery backend.
- Check the application's bound model list to confirm that the selected model supports tool calling capabilities and has the corresponding permission switch enabled.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.