Skip to main content
Glama

get_content_plan

Read-onlyIdempotent

The workspace's content plan, from its own publishing history: which formats (reels, carousels, stories, photo posts) are working, a verdict and reason for each, the posting cadence to aim for with suggested weekday and hour slots, and how last week went against it.

Built from the last ~90 days of published posts and the insights already cached on them, so it is only as current as those. It is saved and served for 6 hours; pass refresh=true to rebuild it now (e.g. right after posting a lot). Slot weekdays here are 0=Monday … 6=Sunday, which is NOT the Sunday-first numbering of posting_days in list_workspaces; hours are in the workspace's timezone — if it has none configured, UTC is used, so check list_workspaces first. A workspace with little history gets a thin plan; say so rather than over-reading it. For the raw numbers use the analytics tools.

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_content_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
recapNo
cadenceYes
summaryYes
total_postsYes
generated_atYes
format_verdictsYes
cadence_rationaleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 the data source and staleness window (~90 days of published posts plus cached insights), the 6-hour cache with an override path, and the timezone fallback to UTC. It also warns that low-history workspaces produce a thin plan, which is exactly the kind of caveat an agent needs to interpret results honestly.

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?

Purpose is front-loaded and every sentence carries information — cache TTL, weekday numbering, timezone, low-history caveat. The sentences are long and multi-clause, packing several constraints into each, which makes it dense to parse but not padded.

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?

For a two-parameter read tool with an output schema, the description covers the remaining risk surface: data freshness, cache behavior, timezone and weekday conventions, and the low-history failure mode. Nothing an agent needs in order to call it correctly or interpret its output is missing.

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%, so the description must carry the burden. It fully explains refresh (rebuild the cached plan now, with a triggering example) and gives implicit meaning to workspace_id via the timezone/lookup discussion. The workspace_id semantics are only partially covered, keeping this just 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?

The opening sentence names a specific resource (the workspace's content plan) and enumerates exactly what it returns: format performance verdicts, posting cadence with weekday/hour slots, and last week's results. It also explicitly routes raw-number needs to the analytics siblings, so an agent can distinguish it from get_account_analytics, get_analytics_summary and get_weekly_recap 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?

It states when to refresh (refresh=true, e.g. right after posting a lot), what to check first (list_workspaces for timezone configuration), which alternative to use for raw numbers (the analytics tools), and how to handle thin results (say so rather than over-reading). Exclusions and prerequisites are both present, leaving little 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