SuperPost

Get content context

get_context

Read-onlyIdempotent

Reads account-scoped context for a content variant, idea, post, assistant thread, publication, schedule, or exact source capture. A source_capture returns its exact saved text and verified provenance, including manual captures outside the bounded initial references; direct Google-derived or unverified source content remains withheld. The external OAuth Read SuperPost data disclosure includes saved post text with unknown source provenance; known Google-derived post text is available only when the current, versioned Google post-content disclosure was accepted for this connection. Direct Google source files, images, video bytes, and transcription remain separately restricted by provider permissions and source grants. A post returns full shared text and platform variants when the session has the required post-content access. Thread and publication context is metadata-only. Idea context includes the saved assistantBrief when present and the full generationReceipt when available. assistantBrief is saved writing guidance for a future post and is separate from the thesis, conclusion, and post body. The receipt may contain model name, platform/cadence selection, concise explanation, explanation-cited evidence IDs, context evidence, and context status/hash; fields absent from the receipt were not saved and must not be inferred. MCP-authored receipts preserve the submitted user-facing generation note and omit model, platform selection, or evidence when the tool did not provide them. Cited evidence IDs are distinct from the broader providedEvidence list. The explanation is a saved rationale, not private chain of thought; older ideas may have no receipt.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "get_context"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`kind`	Yes	source_capture identifies an exact source capture, including manual captures, whose saved text and provenance are available in account-scoped context.

Output Schema

Name	Required	Description	Default
`object`	Yes
`visible`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered; the description goes further by disclosing access gating (Google-derived or unverified content withheld, post text requiring post-content access and accepted versioned disclosure, provider permission limits on files/images/video/transcription). It also warns that absent receipt fields must not be inferred and clarifies that the explanation is a saved rationale, not chain of thought. These are genuine behavioral facts beyond the annotations, though the density of conditional gating makes some rules hard to apply quickly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in sentence one, and nearly every sentence carries substantive information with little repetition. But the body is a dense multi-clause block covering disclosure, provenance, and per-kind return shapes, which is hard to scan and could be restructured into per-kind lines without losing content.

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 only two parameters, full required coverage, an output schema present, and rich annotations, the description supplies everything an agent needs: the valid kinds, what each returns, what is withheld, and how to interpret receipt fields. Nothing material about calling this tool 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 only 50%: the kind enum is documented while id is not. The description compensates by pinning what each kind identifies and by adding meaning to source_capture ('including manual captures outside the bounded initial references') and to what a post, thread, publication, and idea resolve to. The id parameter's meaning is only indirectly conveyed as the identifier of the named kind's entity.

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 first sentence gives a specific verb (reads) and resource (account-scoped context) and enumerates exactly the seven entity kinds the agent can request, matching the schema enum. It is clearly the context-fetch tool rather than a listing tool, though it never names a sibling alternative to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through per-kind outcome descriptions (source_capture returns exact saved text and provenance; thread and publication are metadata-only), which helps an agent pick a kind. However, there is no explicit statement of when to use this tool versus e.g. list_ideas or search_sources, and no stated prerequisites before calling.

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

All SuperPost 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?