Total CMS

get_object

Read-onlyIdempotent

Fetch a single object by its id from a collection. Returns the full object as a flat map of fields, decorated with a url field where the collection has a public URL pattern configured. This tool does not search or filter — use query_collection for paginated lists or search_collection for free-text search.

Available collections and filterable properties:

articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable)
comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable)
extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)
guides — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable), kind (select), product (select)
releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle)
showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)
starters — id (id, sortable), name (text), job (text), useCase (select), siteName (text), summary (textarea), status (select), package (text), buildCommand (text), coreStarter (select), minEdition (select), minVersion (text), demoUrl (url), repoUrl (url), featured (toggle), draft (toggle), updated (datetime, sortable)
streams — id (id, sortable), title (text), date (date, sortable), summary (textarea), release (select), draft (toggle)
studio-app — id (id, sortable), summary (textarea)

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": {
      "collection": "<collection>",
      "id": "<id>"
    },
    "name": "get_object"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Object id (slug). Get candidate ids from query_collection or search_collection output.
`format`	No	Rendered format for content fields. Accepted now for forward-compat; full conversion ships with the Tiptap→markdown converter in a later release.	markdown
`locale`	No	BCP 47 locale tag. Accepted for forward-compat with the 3.6 i18n release — has no effect today.
`collection`	Yes	Collection id. Use list_collections to discover available collections.

Output Schema

Name	Required	Description	Default
`id`	Yes	Object id (slug).
`url`	No	Public URL for this object when the collection has a URL pattern configured.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the response is a flat field map with a `url` field injected only when the collection has a public URL pattern configured. It does not discuss auth or draft/visibility behavior, keeping 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.

Conciseness3/5

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

The purpose and routing sentences are front-loaded and waste-free. However, the trailing block dumps every filterable property for nine collections — most of that metadata governs filtering, which this tool explicitly does not do, making it bulk that the agent must scan past to find the by-id behavior.

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?

Rich annotations, an output schema, and fully described parameters mean little is required of the description, and it covers the essentials: scope, alternatives, return shape, and the valid collection set. Minor gaps remain around visibility (drafts) and permissions, but the tool's complexity is low enough that these are not blocking.

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%, so the baseline is 3, but the description earns more by enumerating the actual valid `collection` values (articles, comparisons, extension, guides, releases, showcase, starters, streams, studio-app) with their field sets — far more useful than the schema's misleading examples 'blog' and 'products'. The per-collection 'sortable'/'filterable' tags are only meaningful for the query/search tools, so the list is not optimally framed for a by-id fetch.

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?

Opens with a specific verb and resource ('Fetch a single object by its id from a collection') and immediately states the return shape ('full object as a flat map of fields'). It also explicitly contrasts itself with query_collection and search_collection, so an agent can distinguish it from siblings without reading 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 an explicit when-not ('This tool does not search or filter') followed by the two named alternatives and the condition that selects each (paginated lists vs. free-text search). The id parameter description repeats the routing by telling the agent to get candidate ids from those same tools.

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

All Total CMS tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.