jotae-mcp

apply_timeline

Apply a timeline to an event to instantly create all associated automations, including WhatsApp and email sequences. Use after event creation to streamline setup.

Instructions

Aplica uma timeline a um evento, criando todas as automações de uma vez. Use após criar o evento.

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": {
      "event_id": "<event_id>",
      "timeline_id": "<timeline_id>"
    },
    "name": "apply_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes	ID do evento
`timeline_id`	Yes	ID da timeline

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Jun 27, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Discloses that it creates all automations at once (bulk operation). However, without annotations, it does not mention whether it is destructive, requires specific permissions, or what happens to existing automations. Adequate but lacks depth.

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?

Two sentences, front-loaded with the action, no unnecessary words. Efficient and clear.

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

Completeness3/5

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

With 2 required params and no output schema, the description gives the high-level operation but omits details about success indicators or whether automations are overwritten. Adequate but could be more complete for a bulk operation.

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 baseline is 3. The description does not add any additional meaning beyond the schema's brief descriptions of event_id and timeline_id.

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?

Clearly states the verb 'Aplica' (apply) and the resources (timeline to event). Distinguishes from sibling tools like create_automation by specifying it creates all automations at once.

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?

Provides explicit context: 'Use após criar o evento' (use after creating the event). Does not list alternatives or when not to use, but sibling context implies individual automation creation via create_automation.

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