Skip to main content
Glama

Connect lists to outreach and searches

spur_connect_list_automation
Destructive

Link/unlink a workflow, enroll a whole list, attach/detach a search automation. Linking a workflow immediately enrolls current members. Approve the audience, workflow and future automatic outreach before connecting.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description does add value beyond that with "Linking a workflow immediately enrolls current members," a real side effect not visible in structured fields. It still leaves the effects of unlinking and detaching unexplained.

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 sentences plus a closing instruction, front-loaded with the action list, with no filler. The final sentence ("Approve the audience, workflow and future automatic outreach") is slightly vague in wording but still earns its place as a consent gate.

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 destructive, open-world, multi-action tool the description covers all five actions, discloses the enroll-on-link side effect, and states the approval requirement. Gaps remain around what unlinking and detaching actually undo and whether confirm is needed for detach_search, which the schema shows it is not.

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 reported at 100%, and the schema already constrains action, requires confirm with a detailed description, and enforces the oneOf variants, so the baseline is 3. The description's action phrasing loosely echoes the enum values but adds no format, identifier or conditional-requirement detail the schema lacks.

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 names the concrete verbs and resources the tool handles (link/unlink a workflow, enroll a list, attach/detach a search automation), which maps one-to-one onto the action enum in the schema. An agent can tell what the tool does, though it does not distinguish this tool from siblings such as spur_manage_search_automation or spur_create_search_automation.

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 closing sentence gives a precondition ("Approve the audience, workflow and future automatic outreach before connecting"), which tells the agent to obtain user consent first. However, it never says when to pick this tool over a sibling for linking or managing automations, and there is no explicit when-not guidance.

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