Meta Council

Create Outreach Pitch

create_outreach_pitch

Create a reusable pitch template (subject + body templates, optional drafting prompt) owned by the user. Provenance is stamped source="agent" server-side. Returns the new pitch id. Requires authentication.

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": {
      "name": "<name>",
      "subject_template": "<subject_template>",
      "body_template": "<body_template>"
    },
    "name": "create_outreach_pitch"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Pitch name (required).
`tone`	No	Optional tone (default 'professional').
`prompt`	No	Optional AI drafting instruction.
`category`	No	Optional category label.
`body_template`	Yes	Email-body template (required).
`target_segment`	No	Optional target segment label.
`subject_template`	Yes	Subject-line template (required).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null

AddedJul 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations are all false, indicating no read-only, idempotent, or destructive hints, but the description clearly states it creates a resource and requires authentication. It adds provenance stamping and return of pitch id, which is useful beyond annotations. However, it doesn't disclose details like ownership implications or whether duplicate names are allowed.

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?

The description is concise, with three sentences that state the function, key structural elements, ownership, provenance, return value, and authentication requirement. No fluff, and important details are front-loaded.

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 creation tool with full schema coverage and no output schema, the description provides necessary context: ownership, provenance, return value, and auth. It could mention what happens on duplicate names or whether the tool is idempotent, but given the tool's simplicity, this is nearly complete.

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 description coverage is 100%, so the schema already documents each parameter. The description adds the purpose of the templates but doesn't add detail on the 'prompt' parameter's relationship to drafting. Baseline 3 is appropriate because the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that it creates a reusable pitch template with subject and body templates, owned by the user. It distinguishes itself from related tools like create_outreach_campaign by focusing on templates, though it doesn't explicitly name a sibling to differentiate from.

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 when a reusable pitch template is needed, and notes provenance and authentication requirements. However, it does not explicitly state when to use this over create_outreach_campaign or draft_outreach_email, or provide exclusions.

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

All Meta Council 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?