Skip to main content
Glama

Read the content queue with scores

get_content_queue
Read-only

The space's drafts as the user sees them: text, platform, status, tags, planned date, media (image/video), the post it quotes, schedule state, and the reviewer's score / verdict / one-line fix. FREE. Use it to present drafts one by one, to read back how drafts scored, and to pull a slice of the content plan: filter by tag (e.g. a campaign week), platform, or planned date window (planned_from / planned_to, YYYY-MM-DD; orders by planned date). status: active (default — pending + reviewed + staged), pending, reviewed, staged (approved, awaiting publish), scheduled (already in the user's scheduler — read-only), discarded, all (everything but discarded). counts are space-wide totals. Call get_content_draft for one draft's per-axis score and earlier versions.

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": {
      "space_id": "<space_id>"
    },
    "name": "get_content_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly drafts with this tag (exact), e.g. "Communities week".
limitNo
statusNo
platformNoOnly this platform label (exact), e.g. "Lior X".
space_idYes
planned_toNoPlanned on or before this date (whole day) or ISO time.
planned_fromNoPlanned on or after this date (YYYY-MM-DD) or ISO time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / planned_from
      Added value: +{
      +  "description": "Planned on or after this date (YYYY-MM-DD) or ISO time.",
      +  "type": "string"
      +}
    • addedInput schema / properties / planned_to
      Added value: +{
      +  "description": "Planned on or before this date (whole day) or ISO time.",
      +  "type": "string"
      +}
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Only this platform label (exact), e.g. \"Lior X\".",
      +  "type": "string"
      +}
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "active",
      -  "pending",
      -  "reviewed",
      -  "staged",
      -  "discarded"
      -]New value: +[
      +  "active",
      +  "pending",
      +  "reviewed",
      +  "staged",
      +  "scheduled",
      +  "discarded",
      +  "all"
      +]
    • addedInput schema / properties / tag
      Added value: +{
      +  "description": "Only drafts with this tag (exact), e.g. \"Communities week\".",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real context beyond that: it states the default status (active = pending + reviewed + staged), that scheduled drafts live in the user's scheduler and are read-only, that counts are space-wide totals, and that results are ordered by planned date. Gaps remain around pagination and what happens when limit is hit, which keeps it short of a 5.

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?

Purpose, cost, use cases, filters, and the sibling alternative arrive in a single front-loaded paragraph with no filler; the parentheticals carry substantive meaning (enum expansions, date format, ordering) rather than repetition. Dense but every clause earns its place.

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?

With no output schema, the description carries the burden of describing return values and does so by enumerating every field, including counts semantics. The only omission for a 7-parameter listing tool is limit/pagination behavior.

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 only 57%, but the description compensates by defining every status enum value in plain language, giving date formats for planned_from/planned_to, specifying exact-match semantics for tag and platform, and noting date ordering. limit and space_id are left to the schema, which is a minor residual gap.

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?

Names a specific verb and resource and enumerates exactly what the record contains (text, platform, status, tags, planned date, media, quote, schedule state, reviewer score/verdict/fix). It also distinguishes itself from the sibling get_content_draft, which is explicitly reserved for one draft's per-axis score and earlier versions.

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?

Gives three concrete use cases (presenting drafts one by one, reading back scores, slicing the content plan) plus explicit filter dimensions and an ordering rule. It also names the alternative tool and the condition that selects it: call get_content_draft for a single draft's per-axis detail or version history.

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.