Skip to main content
Glama
CFP-102

cfp-seo-agent

by CFP-102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

content_plan_shift

Idempotent

Move one content calendar date and shift linked concept-to-publish steps in order. Grouped shoot days move together, finished steps stay fixed, and a returned change list supports confirmation.

Instructions

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. LOCAL (development): calculated on our server from built-in rules and data, no payment. 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.

Input Schema

NameRequiredDescriptionDefault
moveYes
postsYes
languageNode (default) or ende
holiday_regionNonone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • 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"
+}
  2. Changed2 schema fields changedv0.1.4
    • 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]+$"
  3. Addedv0.1.2

TDQS

B3.4/5.0
Behavior1/5

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

The description says the service is stateless, nothing is stored, and "nothing is written anywhere by this service," while annotations declare readOnlyHint=false. That directly contradicts the read-only/no-write claim; the otherwise useful behavioral details cannot override this inconsistency.

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 purpose is front-loaded and the description is informative, but it is overlong and repetitive. The return fields are listed twice, and the confirmation-flag explanation is repeated, adding bulk without new meaning.

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 complex nested tool with no output schema, the description is largely complete: it lists return fields, explains statelessness, limits input to non-personal data, and states that confirmation should precede applying changes. The main gap is that holiday_region is never explained, and the annotation contradiction creates residual ambiguity.

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?

With only 25% schema description coverage, the description must compensate. It explains the date-chain semantics, finished steps, shared shoot days, the 40-post limit, language, and confirmation flag, but it omits the purpose of holiday_region and does not clarify the detach or only_publish modes beyond what the schema already says.

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 states a specific verb and resource: "Move one date in a content calendar" and explains the linked-step behavior. It clearly distinguishes this focused rescheduling operation from broader planning siblings such as content_month_plan or 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use it: moving one date and letting dependent content steps follow. It does not explicitly compare alternatives or state when not to use it, but the operational context is unambiguous.

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

Deploy Server

Other Tools