Skip to main content
Glama

Start a new outreach setup

new_outreach

A fresh outreach generation of the search: empty, or with this search's previous setup (reuse_previous) or a saved one (preset_id). Free; the first paid setup step of the generation spends one brief. [REST: POST /api/tasks/{id}/outreach/new]

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": {
      "task_id": "<task_id>"
    },
    "name": "new_outreach"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe search id (task id), e.g. from list_searches or create_search.
preset_idNo
generation_idNoThe outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
reuse_previousNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description adds genuinely useful behavioral context: the operation is free, and the first paid setup step of the generation spends one brief. That cost/credit disclosure is exactly the kind of context annotations cannot carry. It does not say what happens to any pre-existing generation, which is the main remaining gap.

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?

Two short segments with no filler, and the mode enumeration comes before the cost note. The elliptical 'A fresh outreach generation of the search' opener is terse to the point of being harder to parse than a plain verb phrase would be, but nothing is wasted.

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?

For a non-idempotent mutation with four parameters and no output schema, the definition covers modes and cost but remains incomplete: it never states what a call returns (for example, the new generation id) or what happens when a generation already exists. The ambiguity with the start_outreach sibling is also left unresolved.

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 50%, with preset_id and reuse_previous undocumented in the schema, but the description compensates by explaining both: reuse_previous reuses this search's previous setup and preset_id applies a saved preset. It adds no meaning for generation_id beyond the schema and does not explain the accepted id format, but it closes the most important semantic gap.

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

Purpose3/5

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

The description identifies the resource (a new outreach generation of a search) and enumerates the three starting states: empty, reuse_previous, or preset_id. However, it is written as a noun fragment with no explicit verb, and it never distinguishes itself from the similarly named sibling start_outreach, which an agent could easily confuse with this tool.

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?

Usage is only implied: the three modes hint at when to pick each option, but there is no explicit statement of when to use this tool versus start_outreach, retry_outreach, or continue_search. It also omits prerequisites, such as whether an outreach generation must not already be in progress.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources