Skip to main content
Glama

Set the accounts

set_outreach_funnel
Idempotent

«Аккаунты»: what the user can write from — email (bool), linkedin (none | basic | sales_navigator), threads (bool), linkedin_comments (public comments on LinkedIn posts, bool). At least one. The route of each person's messages is chosen from these. [REST: PUT /api/tasks/{id}/outreach/funnel]

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>",
      "email": "<email>",
      "linkedin": "<linkedin>",
      "threads": "<threads>"
    },
    "name": "set_outreach_funnel"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare openWorld=false, idempotent=true, destructive=false, so safety is largely covered. The description adds genuine context beyond that — the minimum-one-channel rule, that routing of each person's messages derives from these settings, and the underlying PUT endpoint — but says nothing about prerequisites, side effects on running outreach, or permissions.

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?

Compact and front-loaded: the resource is named first, then each field's meaning, then the minimum-one rule and its behavioral consequence, with the REST endpoint appended. No wasted sentences.

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 6-parameter mutation with no output schema, the parameter semantics are adequately covered, but an agent still lacks context on prerequisites (generation_id default behavior is only in the schema), effect on in-flight outreach, and how this relates to sibling outreach tools.

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 description coverage is only 33%, and the description compensates well by defining all four undocumented fields: email and threads as booleans, linkedin's three-valued enum, and explicitly that linkedin_comments means public comments on LinkedIn posts. Only task_id and generation_id go unexplained, and both carry schema descriptions.

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 explains that this configures the "«Аккаунты»" — the channels the user can write from — and its effect on message routing, which is more than a restatement of the name. However, the framing is cryptic (a Russian label plus "Set the accounts") and never clearly says this sets a task's outreach funnel, nor distinguishes it from siblings like set_outreach_sender or set_outreach_essence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only guidance is the constraint "At least one" channel must be enabled. There is no statement of when to call this versus the sibling outreach-configuration tools, no prerequisites (e.g. an existing outreach generation), and no note on when not to use it.

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