cfp-seo-agent

shoot_day_plan

Idempotent

Bundle up to 12 planned videos into balanced, location-based shoot days with timed schedules, breaks, equipment lists, checklists, and optional .ics calendar files.

Instructions

Turn up to 12 planned videos into realistic shoot days: bundled by place, split evenly (max 3 shoots, 8 h), with set-up, breaks, lunch, timed schedule, equipment list, checklist and optional .ics files. Returns: JSON with language, rules, summary, days, warnings, coverage. LOCAL (development): calculated on our server from built-in rules and data, no payment. NOTE: Rule-based, German labels, no AI model. Do not send names or other personal data: only video titles, place labels and equipment. Results are kept 30 days like all results. Nothing is written to a calendar; calendar files are text you import yourself.

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": {
      "shoots": "<shoots>"
    },
    "name": "shoot_day_plan"
  }
}

Input Schema

Name	Required	Description	Default
`shoots`	Yes
`language`	No	de (default) or en	de
`first_date`	No	Optional YYYY-MM-DD of the first shoot day; adds calendar files. Further days follow every second day.
`start_time`	No		09:00
`break_minutes`	No
`lunch_minutes`	No
`max_day_minutes`	No
`max_shoots_per_day`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.4Oct 24, 2026
- changedInput schema / properties / shoots / items / properties / equipment / items / pattern
```
Previous value: -"^[^\\u0000-\\u001f\\u007f]+$"New value: +"^[^\\x00-\\x1f\\x7f]+$"
```
- changedInput schema / properties / shoots / items / properties / location / pattern
```
Previous value: -"^[^\\u0000-\\u001f\\u007f]+$"New value: +"^[^\\x00-\\x1f\\x7f]+$"
```
- changedInput schema / properties / shoots / items / properties / title / pattern
```
Previous value: -"^[^\\u0000-\\u001f\\u007f]+$"New value: +"^[^\\x00-\\x1f\\x7f]+$"
```
Addedv0.1.2Oct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Despite annotations, it adds substantial disclosure: deterministic rule-based (no AI model), German labels, no payment, nothing written to a calendar (files are text you import), 30-day result retention, and a privacy constraint against sending personal data. This is rich context beyond the annotation set.

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?

Front-loaded with the core transformation, then returns, then operational notes; nearly every clause carries information. It is dense and slightly paragraph-heavy, but not padded.

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 complex 8-parameter tool with no output schema, it covers inputs, return structure (language, rules, summary, days, warnings, coverage), constraints, privacy, and determinism. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate, and it does: it explains bundling by place, max 3 shoots/day, 8h days, set-up/breaks/lunch, language, and optional .ics via first_date. It leaves start_time and the numeric ranges for breaks/lunch less explicit, so not a full 5.

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: 'Turn up to 12 planned videos into realistic shoot days,' and enumerates the concrete outputs (schedule, equipment list, checklist, .ics). An agent knows exactly what this tool produces 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 Guidelines3/5

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

The description implies usage by referencing 'planned videos' and 'recipe_id from video-recipes', but never states explicitly when to use this versus siblings like video_project_plan, content_month_plan, or shoot_location_check. Usage must be inferred from context.

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