Skip to main content
Glama

Saved outreach setups

list_outreach_presets
Read-onlyIdempotent

The user's saved outreach setups across searches (sender, offer, ask, language, accounts, source search), newest used first; new_outreach with preset_id copies one into a fresh generation. [REST: GET /api/outreach/presets]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_outreach_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered without prose. The description adds value beyond that by disclosing the sort order (most recently used first) and the shape of each preset item, which is what an agent needs to decide whether to page or to go straight to new_outreach. It stops short of describing how many items a typical user has or whether presets persist across searches.

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?

A single front-loaded sentence carries the resource, its fields, the ordering, and the follow-up action, with the REST route tucked into a bracketed tag at the end. Nothing is redundant. The nesting of the field list inside the sentence is slightly dense to parse but does not cost clarity.

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 two-parameter read-only list with no output schema, the description covers what is returned, how it is ordered, and what to do next. The one material gap is pagination: with a default limit of 25 and no explanation of cursor, an agent may under-fetch and believe it has seen every preset.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden for both parameters and does not mention either. limit has usable constraints in the schema (default 25, max 50), but cursor is only typed as a string with maxLength 200, and nothing in the description explains that results are paginated or how to continue past the first page. An agent cannot tell from either source whether it must loop on cursor to see all presets.

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 user's saved outreach setups across searches" names a specific resource and scope, and the parenthetical enumerates the fields each preset carries (sender, offer, ask, language, accounts, source search). The ordering rule "newest used first" further pins down what is returned. It does not name an explicit verb, but the resource and scope are unambiguous enough that an agent can distinguish it from list_searches or get_outreach.

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?

The description gives concrete routing: "new_outreach with preset_id copies one into a fresh generation," which tells the agent exactly what to do with a returned preset rather than treating this list as an end in itself. What is missing is an explicit when-not-to-use condition (e.g. how this differs from list_previous_onboardings or list_plans when looking for prior setups), so the guidance is clear but not exhaustive.

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