Skip to main content
Glama

Get account analytics

get_account_analytics

Get analytics metrics for a connected social account. Empty/available=false is not an error (see reason: NOT_SUPPORTED for networks without analytics such as WordPress and LinkedIn; e.g. NOT_AVAILABLE or PROVIDER_ERROR when a YouTube channel has not granted the Analytics API or YouTube rejected the call); the window must end today (or yesterday), max 90 days, and is served as the trailing 7/30/90 days (the response range shows the window actually used); for a BLUESKY account the response carries impressions and reach as {available:false, reason: NOT_PROVIDED_BY_NETWORK} because Bluesky does not expose them (never treat that as zero or as an error); a GBP account is a location and its analytics are per location: a location the connection can no longer access returns available=false with a reason (NOT_AVAILABLE or PROVIDER_ERROR), never an error; requires scope ANALYTICS_READ (the key can only be created by the workspace owner).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>"
    },
    "name": "get_account_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRange end, ISO date YYYY-MM-DD.
fromNoRange start, ISO date YYYY-MM-DD.
channelNoChannel of the account, e.g. INSTAGRAM (UPPERCASE canonical, lowercase accepted).
accountIdYesConnected social account id (uuid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: available=false is explicitly not an error, per-provider reasons are enumerated (NOT_SUPPORTED, NOT_AVAILABLE, PROVIDER_ERROR), Bluesky's impressions/reach are flagged as never-to-be-treated-as-zero, GBP per-location semantics are explained, and the required ANALYTICS_READ scope plus owner-only key creation are disclosed.

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

Conciseness3/5

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

The content mostly earns its place, but it is delivered as one long run-on sentence with deeply nested parentheses rather than front-loaded bullets. The important constraints (window, scope) are buried mid-stream behind a parenthetical about error reasons.

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

Completeness4/5

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

No output schema exists, and the description does cover key response fields (range, impressions, reach, available/reason), which is the right compensation. It still doesn't sketch the general metrics payload shape, leaving the agent to discover the main metric fields at call time.

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 would be 3, but the description adds genuine meaning: it constrains the from/to window (must end today/yesterday, 90-day cap, snapped to trailing 7/30/90 with the actual range echoed back) and gives channel-specific behavior for BLUESKY and GBP.

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

Purpose4/5

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

Opens with a specific verb+resource: 'Get analytics metrics for a connected social account,' which scopes it to account-level rather than post-level analytics. It doesn't explicitly name a sibling such as get_post_metrics to separate the two, so the distinction must be inferred from the word 'account'.

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

Usage Guidelines3/5

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

Gives real operating constraints — the window must end today or yesterday, max 90 days, served as trailing 7/30/90 days — which tells the agent how to call it validly. It never states when to prefer this over post-level or best-time analytics tools, so alternative selection is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources