Marcora

get_content

Read-onlyIdempotent

Retrieves the full markdown body of a specific content document by its content_id (UUID).

**Always warranted: reading a project's BRIEF.** When `get_project` or `get_relevant_context` returns a `project_brief` block with `truncated: true`, call this tool with that `content_id` before drafting, revising, assessing or critiquing anything in that project. The brief states the premise and the structural decisions already taken, and work produced without it is likely to contradict them. The caution below does not apply to it.

**Otherwise, use this ONLY when you need to read the content body to answer the user's question** — for example: "summarize what my latest case study says about pricing," "what's the main argument in my Q3 launch blog?", or "does this messaging doc mention HIPAA?". The user already has access to view the content in Marcora via its link, so reading the body yourself is only useful when you need to answer something specific about it.

**Do NOT call this after `create_content` (or after `get_generation_status` returns "completed") just to "show the user what was generated."** The user opens the content in Marcora via the link_url — they review it themselves. Marcora hands them the link; the user does the reading.

**Links:** present `link_url` to the user exactly as returned — copy it character for character. Never retype, shorten, or rebuild a link or the IDs inside it.

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": {
      "content_id": "<content_id>"
    },
    "name": "get_content"
  }
}

Input Schema

Name	Required	Description	Default
`content_id`	Yes	UUID of the content to retrieve. Get from list_content, get_project (documents array), or get_generation_status.

Output Schema

Name	Required	Description
`name`	Yes	Content name.
`stage`	No	Enumeration of in_progress or ready.
`content`	Yes	Full document content in markdown format.
`category`	No	Content category, or null if not categorized.
`link_url`	No	Direct URL to view this content in Marcora.
`content_id`	Yes	Content identifier.
`visibility`	No	Visibility setting (e.g. private, team).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the return is the full markdown body (as opposed to the truncated brief block), and the output-handling rule that link_url must be copied character-for-character rather than rebuilt. It does not discuss size limits or errors, but the output schema covers the return shape.

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 in the first line and the bold section headers make scanning easy. It is longer than strictly necessary — the links paragraph, while useful, is output-presentation policy rather than retrieval semantics — but every sentence still carries actionable instruction and none is filler.

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 a full output schema, complete annotations, and a 100%-documented parameter, the description supplies exactly the missing pieces: the truncation escape hatch via project_brief, the trigger conditions for reading a body, and the anti-pattern of re-reading after generation. Nothing an agent needs in order to decide and call correctly is absent.

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 coverage is 100% and the single parameter already documents its own provenance ('Get from list_content, get_project (documents array), or get_generation_status'). The description restates the UUID nature of content_id without adding new semantics, so the baseline of 3 is appropriate.

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 names a specific verb and resource ('Retrieves the full markdown body of a specific content document') and identifies the key ('by its content_id (UUID)'). It is clearly separable from siblings like list_content or get_generation_status, which the description itself references.

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?

Explicit when-to-use cases with concrete user-question examples, an explicit exception where the tool is 'always warranted' (truncated project_brief), and an explicit when-not-to-use ('Do NOT call this after create_content ... just to show the user what was generated') with the alternative explained (user opens link_url in Marcora). This is the strongest form of routing guidance.

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

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

Resources

Need Help?