Skip to main content
Glama

get_entry

Fetch a single Strapi CMS entry with all field data, including nested components and relations. Provide a document_id for collection types; omit it for single types.

Instructions

Fetch a single entry with all its field data. For collection types, provide the document_id (get it from list_entries). For single types, omit document_id — there is only one entry. Returns the full entry including nested components and relations.

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_type": "<content_type>"
    },
    "name": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLocale code
document_idNoDocument ID (required for collection types, omit for single types)
content_typeYesContent type UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose what comes back ('the full entry including nested components and relations'), which is valuable, but it says nothing about permissions, read-only semantics beyond the implied 'Fetch', or error behavior for an invalid identifier.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action, then conditional branching, then return shape. No restated title, no filler, and each sentence contributes a distinct decision-relevant fact.

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 three-parameter read tool with no output schema, the description covers the two things an agent needs: how to target the right entry and what the response contains. Only the absence of locale semantics and error/failure conditions keeps it from being fully self-sufficient.

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%, so all three parameters are already documented, including the collection-vs-single rule for document_id. The description adds only the provenance hint for document_id ('get it from list_entries'); locale and content_type meanings are left entirely to the schema, making this the standard baseline case.

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 definition opens with a specific verb and resource ('Fetch a single entry with all its field data') and immediately clarifies scope by splitting behavior between collection types and single types. It also routes the agent to the sibling tool that supplies the identifier ('get it from list_entries'), so it can be told apart from list_entries without opening either schema.

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 clear conditional guidance: supply document_id for collection types (sourced from list_entries) and omit it for single types. What is missing is any exclusion or failure guidance — nothing says what happens with an invalid document_id or a wrong content_type — but the when-to-use path is unambiguous.

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