Tailwind App

get_account_analytics

Read-onlyIdempotent

Use this when the user asks how their Pinterest account is performing overall — impressions, engagement, saves, clicks — or wants a trend over time: returns account-wide totals plus a per-day series. Covers claimed and unclaimed content alike, the same numbers Pinterest Insights shows in Tailwind. Totals combine paid (promoted) and organic activity unless contentType says otherwise: pass ORGANIC for how unpromoted Pins are doing, or PAID for promoted only. get_pin_analytics figures are always organic-only, so compare them against ORGANIC totals, not the default blend.

This is the account rollup. For the best-performing Pins use list_top_pins; for one Pin use get_pin_analytics. Reading analytics is free and consumes no credits. Omit startDate and endDate for the last 30 days; supply BOTH to choose a window (supplying one is an error). Dates are UTC YYYY-MM-DD. Pinterest reports at most 90 days back and at most a 90-day span. The range actually used comes back as startDate/endDate — report those, do not assume the period. If the user did not say which Pinterest account to use and list_accounts returns more than one, ask the user which account to use before calling this — do not choose for them.

Input Schema

Name	Required	Description
`endDate`	No	Last day of the window (inclusive), UTC YYYY-MM-DD. Requires startDate.
`accountId`	Yes	Numeric Tailwind account ID returned by list_accounts
`startDate`	No	First day of the window, UTC YYYY-MM-DD. Requires endDate. Omit both for 30 days.
`contentType`	No	Which activity to count: ORGANIC for unpromoted performance only, PAID for promoted (ad) performance only, ALL for both blended. Defaults to ALL.

Output Schema

Name	Required	Description
`endDate`	Yes	Last day actually reported on, inclusive
`accountId`	Yes
`startDate`	Yes	First day actually reported on
`contentType`	Yes	The paid/organic filter actually applied
`dailyMetrics`	Yes	Per-day metrics across the window, earliest first
`summaryMetrics`	Yes	Pinterest metrics, camelCased. A null value means Pinterest has not finished computing that metric for that day; an absent one means it does not report it for this subject.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent annotations, it discloses cost ('free, consumes no credits'), hard API limits (90-day lookback and 90-day span), that the effective range is echoed back as startDate/endDate and should be reported rather than assumed, and that totals blend paid and organic by default. That is exactly the kind of behavior an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and scoping constraints, and nearly every sentence carries operational value. A few clauses are mildly redundant with the schema (both dates required, UTC YYYY-MM-DD) and 'This is the account rollup' repeats the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return-shape explanation is unnecessary. Everything else an agent needs to invoke correctly is present: account disambiguation, default window, window limits, enum semantics, cross-tool comparability, and credit cost.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above that by explaining what the ORGANIC/PAID/ALL enum means relationally — get_pin_analytics numbers are organic-only and must be compared against ORGANIC totals, not the blend. Date pairing rules are restated from the schema rather than extended, so it stops short of a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with explicit scope: account-wide totals (impressions, engagement, saves, clicks) plus a per-day series, covering claimed and unclaimed content. It directly distinguishes itself from get_pin_analytics ('the account rollup') and list_top_pins, so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternatives and the condition that selects each: list_top_pins for best-performing Pins, get_pin_analytics for a single Pin. It also gives explicit routing rules for contentType (ORGANIC vs PAID vs default blend) and a disambiguation protocol — ask the user which account when list_accounts returns multiple.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tailwind App tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?