Fetch Pinterest account analytics for impressions, saves, and clicks within a specified date range. Provide start and end dates to receive performance metrics.
Get account-level Pinterest analytics: impressions, saves, clicks. Dates must be in YYYY-MM-DD format.
| Name | Required | Description | Default |
|---|---|---|---|
| metrics | No | ||
| end_date | Yes | ||
| start_date | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. 'Get' implies a read-only operation, but it does not disclose authentication requirements, rate limits, or any other behavioral side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences, front-loading the core purpose and adding only the essential date format constraint. No redundant or irrelevant content is present.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists and the operation is straightforward, the description covers the primary purpose, metrics, and date format. It lacks some optional context like timezone handling or metric value enumeration, but is sufficiently complete for basic usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides no parameter descriptions, so the description must compensate. It explains the date format and names possible metrics, but it does not fully define the metrics parameter (e.g., allowed values, null behavior) or provide details on start/end date semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves account-level Pinterest analytics, listing specific metrics (impressions, saves, clicks). The 'account-level' qualifier distinguishes it from the sibling get_pin_analytics tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use for account-wide analytics and provides date formatting guidance, but it does not explicitly state when to use this tool versus alternatives such as get_pin_analytics or other siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.