Skip to main content
Glama

get_weekly_recap

Read-onlyIdempotent

Last complete week's scorecard: posts published against the plan's cadence per format (hit or missed), and reach, interactions and engagement rate against the week before, with the percentage change.

Uses the saved content plan as the target (it never regenerates it), so plan_available is false — and the per-format targets empty — until the workspace has opened or built a plan: call get_content_plan first in that case. Reads cached insights only; no calls to Instagram. Use it to answer "how was last week?".

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_id": "<workspace_id>"
    },
    "name": "get_weekly_recap"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
noteYes
metricsYes
plannedYes
week_endYes
prior_endYes
publishedYes
per_formatYes
week_startYes
prior_startYes
plan_availableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantial behavioral context: it reads from the saved content plan and never regenerates it, and it reads cached insights only with no calls to Instagram. The `plan_available: false` degraded-state behavior is disclosed, which is unusually good for a read tool.

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

Conciseness5/5

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

Front-loaded with the output content in sentence one, followed by precondition and data-source caveats, then a closing usage cue. Every sentence carries distinct information and none repeats the name or annotations.

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?

An output schema exists, so return values need not be spelled out, and the description still flags the two fields an agent must check (`plan_available` and per-format targets) along with the recovery path. For a one-parameter, plan-dependent read tool this is complete.

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 0%, but there is only a single `workspace_id` parameter whose meaning is self-evident, so the burden is light. The description adds real meaning by tying the workspace to precondition state: targets remain empty until that workspace has opened or built a plan.

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 first sentence states a specific verb and resource ('last complete week's scorecard') and enumerates exactly what is reported: posts published versus the plan's cadence per format with hit/miss, plus reach, interactions and engagement rate versus the prior week with percentage change. That level of specificity makes it distinguishable from general analytics siblings such as get_account_analytics or get_analytics_summary without opening their schemas.

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 names an explicit prerequisite and routing rule: when `plan_available` is false and per-format targets are empty, call get_content_plan first. It also closes with a concrete when-to-use cue ('answer "how was last week?"'). It stops short of saying when to prefer this over the account- or reel-level analytics siblings, so it is clear context rather than a full alternatives map.

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