Skip to main content
Glama

Export SDR contacts to an audience

sdr_export_personas_to_audience

Creates a custom audience from a search's contacts with an email (segment fit by default, optional roles or explicit ids). No credits. The audience can then be used in any campaign.

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": {
      "search_id": "<search_id>",
      "name": "<name>"
    },
    "name": "sdr_export_personas_to_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
nameYesName of the new audience
rolesNo
search_idYes
fit_segmentNo
only_with_emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / fit_segment
      Added value: +{
      +  "enum": [
      +    "fit",
      +    "fit_uncertain",
      +    "all",
      +    "uncertain",
      +    "unfit",
      +    "unchecked"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / ids / items / $ref
      Added value: +"#/properties/search_id"
    • removedInput schema / properties / ids / items / type
      Removed value: -"string"
    • addedInput schema / properties / name / description
      Added value: +"Name of the new audience"
    • addedInput schema / properties / name / maxLength
      Added value: +200
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / search_id / format
      Added value: +"uuid"
    • changedInput schema / required
      Previous value: -[
      -  "search_id"
      -]New value: +[
      +  "search_id",
      +  "name"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that the operation creates a custom audience, requires contacts with an email, defaults to fit segment, and consumes no credits, but it omits permissions, duplicate-handling, side effects, and error behavior.

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 two tight sentences and front-loads the core action and resource. It avoids repetition and includes only relevant caveats such as no credits and downstream campaign use.

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 no-annotation mutation tool with six parameters and low schema coverage, the description covers the core operation but leaves out important behavioral details like permissions, audience naming behavior, return values, and failure cases. It is adequate but incomplete.

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 17%, so the description must compensate. It does add meaning for search_id (source search contacts), fit_segment (fit by default), roles (optional), ids (explicit ids), and only_with_email (contacts with an email), though the name parameter is not discussed.

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 the verb and resource: creating a custom audience from a search's contacts. It adds scope details such as email filtering and segment fit, but it does not explicitly distinguish this from siblings like create_custom_audience or sdr_export_people_csv.

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?

It implies the tool is used to turn an SDR search into a campaign-usable audience and notes segment fit defaults, optional roles, and explicit ids. However, it gives no explicit when-to-use versus alternatives or when-not-to-use 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