Skip to main content
Glama

describe_content_type

Retrieve a Strapi content type's field names, types, required flags, components, relation targets, labels, and descriptions before creating or updating entries to avoid schema mismatches.

Instructions

Get the complete field structure of a content type — field names, types, whether required, component details, and relation targets. Also shows CMS labels and descriptions that content managers see. ALWAYS call this before creating or updating entries to know the exact field names and types expected.

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": {
      "uid": "<uid>"
    },
    "name": "describe_content_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesContent type UID, e.g. "api::home-page.home-page" or "api::news-article.news-article"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the shape of the returned data (field metadata, component nesting, relation targets, plus CMS-facing labels and descriptions). It does not mention permissions, auth requirements, or whether the output is truncated for very large content types, which keeps it below 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.

Conciseness5/5

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

Three sentences, front-loaded with the payload description, followed by the secondary CMS-metadata detail, then the behavioral directive. Every sentence carries information an agent would otherwise have to guess.

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?

For a one-parameter read tool with no output schema and no annotations, the description fully covers both what is returned and when to call it, including the critical fact that field names/types must be known before writing entries. Nothing an agent needs to invoke it correctly is missing.

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?

There is a single parameter whose schema description already covers 100% of its meaning, including concrete UID examples like "api::home-page.home-page". The prose adds no format or validation detail beyond the schema, so the baseline of 3 applies.

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 ("Get the complete field structure of a content type") and enumerates exactly what that structure includes: field names, types, required flags, component details, and relation targets. That is clearly distinct from list_content_types (which enumerates types) and get_entry (which returns data), so an agent can select it without opening the 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?

Gives an explicit, actionable directive: "ALWAYS call this before creating or updating entries," which directly ties it to the create_entry/update_entry workflow steps. It lacks negative guidance (e.g., when it is unnecessary because a schema was already fetched) or naming an alternative, so it falls just short of the top band.

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