Blaze

Get performance digest

get_performance_digest

Read-onlyIdempotent

Get a short performance report for a workspace's connected social accounts. For each account it reports followers and impressions (Instagram reach, Facebook unique impressions, YouTube views, Google Business Profile profile views) for yesterday, the trailing 7 days, and the trailing 30 days, all ending yesterday in the workspace's timezone. Each window is compared with the preceding window of the same length. Followers show the latest total and the net adds in each window.

Inputs: workspace_key; optional period ("daily" or "weekly", default "daily"; weekly also lists up to 5 top posts published in the last 7 days); optional goal_net_followers_per_day (compares the trailing 7-day average of net adds with the goal).

Metrics are collected once a day and can lag or have gaps. Missing values are shown as "—" (null in structured content) with a dated note; they are never estimated. An impressions window is missing if any of its days is missing. Follower net adds only need the totals on the window's first and last days, so they are still shown when days in between are missing, and the note lists those days. Read-only.

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": {
      "workspace_key": "<workspace_key>"
    },
    "name": "get_performance_digest"
  }
}

Input Schema

Name	Required	Description
`period`	No	'daily' (default) or 'weekly'. Weekly adds the week's top posts.
`workspace_key`	Yes	Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.
`goal_net_followers_per_day`	No	Optional target for net new followers per day across all accounts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the freshness model ('metrics are collected once a day and can lag or have gaps'), the null representation ('—' in text, null in structured content), and the precise missing-data rules (impressions window void if any day is missing; follower net adds still shown from window endpoints). Timezone anchoring of windows and the preceding-window comparison are also stated.

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?

Long but organized: purpose first, then what each window contains, then an explicit 'Inputs:' block, then caveats and the read-only note. Almost every sentence carries information, though the metric-to-platform mapping parenthetical adds bulk for marginal selection value.

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?

With no output schema, the description carries the return-shape burden and does so thoroughly: per-account metrics, three windows ending yesterday, comparison to the preceding window, follower totals plus net adds, and null/note semantics. An agent knows what to expect without inspecting a response schema.

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 already 100%, so the baseline is 3, but the description adds meaning: weekly 'also lists up to 5 top posts published in the last 7 days' and goal_net_followers_per_day 'compares the trailing 7-day average of net adds with the goal', which goes beyond the schema's terse 'target for net new followers per day'.

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?

The description names a specific verb and resource ('Get a short performance report for a workspace's connected social accounts') and enumerates exactly which metrics are returned per platform. No sibling tool reports performance data, so the agent can select it immediately.

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

Usage Guidelines4/5

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

It establishes clear context: analytics for a workspace's connected accounts, with the daily-vs-weekly choice and what weekly adds ('up to 5 top posts published in the last 7 days'). It does not name alternatives or exclusions (e.g., list_connected_accounts for account inventory), so it stops short of a 5.

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

All Blaze 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.