jotae-mcp

create_event

Create a new live event by providing a title. Optionally add YouTube URL, start time, and CTA URL for purchase or registration.

Instructions

Cria um novo evento ao vivo. Campos obrigatórios: title. Recomendado preencher youtube_url, event_start e cta_url.

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": {
      "title": "<title>"
    },
    "name": "create_event"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Título do evento
`cta_url`	No	URL do botão de compra/CTA
`cta_label`	No	Texto do botão CTA (ex: "Garantir minha vaga")
`event_end`	No	Data/hora de encerramento ISO 8601
`pitch_end`	No	Fim do pitch ISO 8601
`event_start`	No	Data/hora de início ISO 8601 (ex: 2025-09-10T20:00:00-03:00)
`pitch_start`	No	Início do pitch de vendas ISO 8601
`youtube_url`	No	URL do vídeo no YouTube (ex: https://youtu.be/xxx)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Jun 27, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided; description indicates a mutation operation ('creates') but lacks details on side effects, permissions, or idempotency. Adequate for a standard create tool.

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?

Single sentence concisely conveys purpose and key parameter guidance. No unnecessary words or repetition.

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?

Covers essentials: purpose, required field, and recommendations. Schema handles parameter details. Could add behavior on missing recommended fields or output expectation, but sufficient.

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 100%, but description adds value by highlighting required (title) and recommended (youtube_url, event_start, cta_url) parameters, aiding parameter selection.

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?

Description clearly states it creates a new live event, specifying required field (title) and recommended fields. Distinguishes from sibling tools like update_event and get_event.

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?

Specifies required and recommended fields, guiding agent on minimum input. Does not explicitly state when not to use (e.g., for updates), but context is clear.

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