Skip to main content
Glama

Read content

read_content
Read-onlyIdempotent

[read-only] Read content. mode="list" returns one page of summaries (limit, cursor, fields); mode="get" requires id and returns the full item. Use only the chosen mode's arguments. Full mode definitions: describe_tool {"name":"list_content"} or {"name":"get_content"}. Legacy names list_content and get_content remain callable.

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": {
      "mode": "<mode>"
    },
    "name": "read_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFormat: string; e.g. "id_123". Record identifier returned by the corresponding list or create tool; use a real ID.
modeYesString mode, e.g. "list". list returns paged summaries; get returns one full item and requires id.
limitNoInteger, e.g. 20. Items per page (1-50, default 20).
cursorNoOpaque string, e.g. "eyJvIjoyMH0". The `nextCursor` of the previous page. Omit for the first page.
fieldsNoString array, e.g. ["id", "title"]. Top-level item fields to return instead of the summary. Default summary: id, contentId, displayTitle, title, type, durationMs, createdAt, postState. For one item in full, use the matching get_ tool.
brandIdNoFormat: string; e.g. "brandId_123". A brand id from GET /api/v2/brands. Omitted: the key's brand (brand-bound key) or the owner's active brand.
includeArchivedNoFormat: boolean; e.g. false. Whether to include archived items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / description
      Previous value: -"String array, e.g. [\"id\", \"title\"]. Top-level item fields to return instead of the summary. Default summary: id, title, type, durationMs, createdAt, postState. For one item in full, use the matching get_ tool."New value: +"String array, e.g. [\"id\", \"title\"]. Top-level item fields to return instead of the summary. Default summary: id, contentId, displayTitle, title, type, durationMs, createdAt, postState. For one item in full, use the matching get_ tool."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered structurally; the description's "[read-only]" prefix merely repeats it. Beyond that it only notes pagination via limit/cursor and that get returns the full item, without describing return shape, empty results, or auth/brand scoping. Useful but thin given how little is added over the structured fields.

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?

Front-loaded with the mode semantics and packed into three tight sentences with no filler. The only waste is the bracketed "[read-only]" tag that restates the annotations, and the describe_tool pointer is a slightly costly indirection but justified for a dual-mode tool.

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?

For a 7-parameter tool with no output schema, the description covers the mode split, argument isolation, pagination signals, and where the fuller mode definitions live. It omits error/empty behavior and any hint about what the returned summary fields mean, which keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the mode description that already states "get returns one full item and requires id" and the conditional use of id. The description's conditional dependency (get requires id, list uses limit/cursor/fields) is therefore largely duplicative rather than additive, so the baseline 3 applies.

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?

The description names a specific verb (read) and splits the tool into two explicitly described modes: "mode=\"list\" returns one page of summaries" and "mode=\"get\" requires id and returns the full item." That is far more than a restatement of the name, though the resource ("content") is left abstract and it never distinguishes itself from sibling mutations such as update_content or delete_content.

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 gives a clear selection rule between the two modes (summaries vs. full item) and the constraint "Use only the chosen mode's arguments," which prevents mixing pagination params with get params. It also routes to describe_tool for full mode docs and notes the legacy list_content/get_content names remain callable. There are no explicit when-not-to-use exclusions, so it falls 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources