Agent Data API

content_plan_shift

Idempotent

Move one date in a content calendar and let the linked dates follow: concept, shoot, edit, review and publish stay in order, a shared shoot day moves all its posts together, finished steps never move. Returns the change list, conflicts, blocked steps, a confirmation flag and the updated posts. Stateless: you send up to 40 posts, nothing is stored. Returns: JSON with language, move, changes, blocked, conflicts, group_change, detached_from_group, needs_confirmation, summary, posts, coverage. PAID: 0.02 USDC per call (USDC on eip155:8453, x402 v2). Requires an x402-capable MCP client that attaches the payment in _meta["x402/payment"] (e.g. createx402MCPClient from @x402/mcp). Without a payment this tool returns a "payment required" result and charges nothing. NOTE: Pure date arithmetic, German or English messages (language), no AI model. Send keys, optional short titles and dates only, no personal data. A confirmation flag means you should review the change list before you apply it to your own calendar; nothing is written anywhere by this service.

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": {
      "posts": "<posts>",
      "move": "<move>"
    },
    "name": "content_plan_shift"
  }
}

Input Schema

Name	Required	Description	Default
`move`	Yes
`posts`	Yes
`language`	No	de (default) or en	de
`holiday_region`	No		none

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / holiday_region

Added value: +{
+  "default": "none",
+  "enum": [
+    "none",
+    "DE-BW",
+    "DE-BY",
+    "DE-BE",
+    "DE-BB",
+    "DE-HB",
+    "DE-HH",
+    "DE-HE",
+    "DE-MV",
+    "DE-NI",
+    "DE-NW",
+    "DE-RP",
+    "DE-SL",
+    "DE-SN",
+    "DE-ST",
+    "DE-SH",
+    "DE-TH",
+    "AT",
+    "CH"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 24, 2026
- changedInput schema / properties / posts / items / properties / shoot_group / pattern
```
Previous value: -"^[^\\u0000-\\u001f\\u007f]+$"New value: +"^[^\\x00-\\x1f\\x7f]+$"
```
- changedInput schema / properties / posts / items / properties / title / pattern
```
Previous value: -"^[^\\u0000-\\u001f\\u007f]+$"New value: +"^[^\\x00-\\x1f\\x7f]+$"
```

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / language

Added value: +{
+  "default": "de",
+  "description": "de (default) or en",
+  "enum": [
+    "de",
+    "en"
+  ],
+  "type": "string"
+}

AddedOct 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

While annotations are sparse, the description provides rich behavioral detail regarding its pure function (German or English messages, no AI model) and detailed return structures (change list, conflicts, blocked steps, confirmation flag). It successfully covers the functional behavior and operational constraints not in the schema/annotations, although the payment details are heavy.

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 description is technically dense and very front-loaded. However, the first sentence is relatively concise, while the subsequent long paragraphs explaining payment, stateless nature, and return structure dilute the immediate actionable information.

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?

Given the high complexity (linked dates, shift modes, payment mechanisms, confirmation requirements, specific status responses), the description provides nearly all the necessary context to use the tool without needing the output schema or exhaustive probing. It clearly outlines both the success and failure conditions.

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?

With schema coverage only at 25%, the description must compensate heavily. It adds value by detailing the specific modes of 'shift' (e.g., 'shared shoot day moves all its posts together') and the implications of 'finished steps never move,' which are semantic rules that go beyond simple type declarations in 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 explicitly states the core function ('Move one date in a content calendar') and details the complex dependency logic ('let the linked dates follow: concept, shoot, edit, review and publish stay in order'). It is highly specific and distinguishable from sibling tools like 'shoot_day_plan'.

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?

It provides critical execution context, stating 'Stateless: you send up to 40 posts, nothing is stored.' Furthermore, it explicitly guides the agent on the success path ('A confirmation flag means you should review the change list before you apply it') and the failure path ('Without a payment this tool returns a "payment required" result').

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

All Agent Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?