Skip to main content
Glama

publish_entry

Makes a Strapi entry live on the website after draft creation or updates; provide document_id for collection types.

Instructions

Publish an entry to make it live on the website. Content in Strapi is draft by default after creation or update. Call this after creating or updating content when the user wants changes to appear on the live site. For collection types, provide the document_id.

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": "publish_entry"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden and it does disclose the key workflow behavior: content is draft by default after create/update, and this makes it live. It does not cover permission requirements, whether republishing an already-live entry is idempotent, or what the response looks like — gaps that matter for a state-changing tool.

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?

Three short sentences, front-loaded with the action and its effect, then the timing, then the one parameter caveat. No filler, though the final document_id sentence partly duplicates the schema.

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 simple three-parameter mutation with no annotations and no output schema, the definition covers purpose, trigger timing, and the draft-default context. Missing only permission/error semantics, which is a modest gap at this complexity.

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 in the schema. The description's note that document_id is needed for collection types repeats the schema wording rather than adding new meaning (e.g., what to pass for single types, or how locale interacts with publishing).

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?

States a specific verb ('publish') plus resource ('an entry') and the concrete effect ('make it live on the website'). An agent can distinguish it from unpublish_entry by the stated outcome, though no sibling is named explicitly.

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 clear timing instruction: call it after creating or updating content when the user wants changes on the live site. It implies the when-not case via 'draft by default' but never states an explicit exclusion or names unpublish_entry as the alternative.

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