microCMS MCP Server

microcms_patch_content_created_by

Change the creator of a content item in microCMS by updating its createdBy field to a specified member ID.

Instructions

Change content creator in microCMS (Management API). Updates the createdBy field of a content item to a specified member ID. Member ID can be found in the member detail screen in the management console.

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": {
      "endpoint": "<endpoint>",
      "contentId": "<contentId>",
      "createdBy": "<createdBy>"
    },
    "name": "microcms_patch_content_created_by"
  }
}

Input Schema

Name	Required	Description
`endpoint`	Yes	Content type name (e.g., "blogs", "news")
`contentId`	Yes	Content ID to change creator
`createdBy`	Yes	Member ID to set as the creator. Member ID can be found in the member detail screen in the management console.
`serviceId`	No	Service ID (required in multi-service mode, optional in single-service mode)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.0May 3, 2026

addedInput schema / properties / serviceId

Added value: +{
+  "description": "Service ID (required in multi-service mode, optional in single-service mode)",
+  "type": "string"
+}

Addedv1.0.0Jan 3, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'Updates the createdBy field' indicating mutation, but fails to mention permissions required, reversibility, side effects, or error conditions. The description carries the full burden but provides minimal behavioral context.

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?

The description is two sentences long, with the first sentence stating the core purpose and the second providing parameter-specific guidance. No extraneous information, well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 parameters, no output schema, and no annotations, the description should provide more context on prerequisites, return values, and error scenarios. It lacks information on what the tool returns after update and conditions for failure. The description is incomplete for an agent to use confidently without additional information.

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 the schema already documents all parameters. The description adds value by repeating the member ID lookup hint, but does not provide new semantics beyond the schema. Baseline 3 is appropriate as the description does not significantly enhance understanding beyond the schema.

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 description clearly states the verb 'Change' and resource 'content creator', specifying it updates the createdBy field to a member ID. This distinguishes it from sibling tools like microcms_patch_content (general updates) and microcms_patch_content_status (status changes).

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?

The description implies usage for changing the creator and provides a hint on finding the member ID, but does not explicitly state when to use this tool over alternatives like microcms_patch_content. No exclusion or when-not-to-use guidance is given.

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