Skip to main content
Glama

Get Outreach Queue

get_outreach_queue
Read-onlyIdempotent

[Read · free] Return a prioritized outreach queue. Provide exactly one of three scopes: • campaign_id — full Constellation queue, one row per person (their best entry's composite_score, pool, recommended_action), with targets[] listing every target they connect to ({target_id, entry_id, composite_score, pool, recommended_action, target_person: {person_id, full_name, current_title}}) and prior outreach_log entries. Pools: coworker = same company as the target (no relationship implied), engager = someone the target engages with, mutual = someone several targets engage with. Pass a target_person.person_id to get_outreach_path to check warm paths. • segment_id — people in a saved audience segment, ranked by their engagement count against your tracked profiles' posts. No composite_score. • linkedin_urls — an ad-hoc list of LinkedIn URLs, same engagement-count ranking as segments. Free — costs 0 credits.

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": "get_outreach_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolNoOptional filter: only return entries in this pool. Only meaningful for `campaign_id` scope; ignored for segment / urls.
limitNoMax entries to return (1-200, default 50)
segment_idNoAudience segment id (engagement-count scoring)
campaign_idNoCampaign id (full Constellation scoring)
linkedin_urlsNoAd-hoc LinkedIn URL list (engagement-count scoring); max 200

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the description earns credit for adding cost behavior ('Free — costs 0 credits') and scope-dependent scoring behavior (composite_score present for campaigns, absent for segments/URLs). It does not discuss pagination beyond limit, response size, or any auth/prerequisite context.

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?

Front-loads the return statement and the exactly-one-scope rule, then uses tight bullets per scope. The parenthetical field enumerations for targets[] and prior outreach_log entries are dense, but with no output schema they carry necessary return-shape information rather than being padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, three-mode read tool with no output schema, the description supplies the per-scope return shape, ranking semantics, and cross-tool handoff. An agent has enough to pick a scope, predict the payload, and know the call is free.

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

Parameters5/5

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

Beyond a 100%-covered schema, it adds real meaning: the mutual exclusivity of campaign_id/segment_id/linkedin_urls (not encoded as a oneOf in the schema), and semantic definitions of the pool enum values (coworker = same company, no relationship implied; engager = target engages with; mutual = engaged by several targets). Those definitions are not derivable from the enum strings alone.

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

Purpose5/5

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

States a specific verb and resource ('Return a prioritized outreach queue') and immediately decomposes it into three named scopes with what each returns. The three scope bullets make the tool's behavior distinguishable from siblings like get_outreach_path and get_post_set_engagers before opening the schema.

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

Usage Guidelines5/5

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

Explicitly instructs 'Provide *exactly one* of three scopes' and explains which scope fits which intent (campaign Constellation scoring vs. saved segment ranking vs. ad-hoc URL list). It also names the alternative for warm-path checks ('Pass a target_person.person_id to get_outreach_path'), giving a concrete when-to-use-elsewhere cue.

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