Marcora

list_content

Read-onlyIdempotent

Lists the team's content (documents the team has created, from scratch or from blueprints) that the current user can see, as a single unified array with consistent field names, newest first. Use it to browse and filter the team's content and to find content IDs.

Use content_id with get_content to retrieve a piece in full. Use create_external_share to share content externally.

Optional search: pass a natural-language query to sort the list by similarity to it instead of recency. Each row then carries a relevance_score (cosine 0–1, higher = more similar). Search only re-orders: every visible row is still returned, with no cutoff, so the response is as large as the team's content. Scores are comparable with list_context_items. To find passages in the reference library that are relevant to a question, use get_relevant_context.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_content"
  }
}

Input Schema

Name	Required	Description	Default
`search`	No	Optional natural-language query. When provided, every visible row is scored by similarity to it and the list is sorted by that score instead of recency; each row gains a relevance_score. Nothing is dropped, so the response is still all of the team's content. Omit or leave empty for the normal recency-ordered list.

Output Schema

Name	Required	Description	Default
`content`	Yes	Returns all content visible to the current user as a single unified array. Content created from scratch and from blueprints are merged with consistent field names.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, yet the description adds substantial behavior: search only re-orders rather than filters, nothing is dropped, so response size scales with total team content — a real cost/latency signal. It also documents the relevance_score scale (cosine 0–1, higher = more similar) and its comparability with list_context_items scores.

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 purpose, then routing, then the search caveat — a sensible order. There is mild redundancy: the 'no cutoff, every row returned, response is as large as the team's content' point is made in the description and again in the schema, and the bold Markdown header is unnecessary for a one-line tool.

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 shapes need not be explained, and the description still surfaces the one output nuance an agent must plan for (relevance_score and unbounded result size). For a single-optional-parameter list tool, nothing needed to call it correctly 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 100% and the parameter's schema text already explains the sort-by-similarity behavior, so the description largely restates it. It does add value beyond the schema by tying the parameter to a relevance_score output field and to cross-tool comparability with list_context_items, which the schema does not mention.

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?

States a specific verb and resource with scope: it lists the team's content (documents created from scratch or from blueprints) that the current user can see, returned newest first as a unified array. The parenthetical definition of 'content' separates it from sibling listers like list_blueprints, list_plans and list_context_items without the agent needing to open any 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?

Gives explicit use cases ('browse and filter the team's content and to find content IDs') and routes to alternatives by task: get_content for full retrieval by content_id, create_external_share for sharing, and get_relevant_context for passages in the reference library. It even states when NOT to use it in the last sentence, which is exactly the differentiation an agent needs.

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?