Skip to main content
Glama

Map Constellation

map_constellation

[Acquire · 1 + 3×targets credits] Map the professional graph around a target company. Finds senior decision-makers at the account, pulls each target's recent posts/reactions/comments to identify engagers, then scores every connection and produces a prioritized outreach queue. The response lists the selected targets (target_id, person_id, full_name, current_title, linkedin_url) and _meta.next_step(s): get_outreach_queue for the scored queue, then get_outreach_path (free) to check warm paths to the top targets. Pools: coworker = other senior people at the same account from the lead search (no relationship with you is implied); engager = someone a target engages with; mutual = someone several targets engage with. Costs at most 1 + 3 × max_targets credits (7 at max_targets=2, 16 at the default 5, 61 at 20): the lead search is a bundled 1 credit, a deliberate discount on linkedin_people_search's 5 credits per page; the balance must cover that worst case, and only what is actually spent is charged and reported in the response.

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": {
      "campaign_account_id": "<campaign_account_id>"
    },
    "name": "map_constellation"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_targetsNoMax targets to deep-map per account (1-20, default 5). Each target adds up to 3 credits.
title_keywordsNoTitle keywords to filter targets. Default: ['VP','Director','Head of','Chief']
campaign_account_idYescampaign_accounts.id — the company to map

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / max_targets / description
      Previous value: -"Max targets to deep-map per account (1-20, default 5). Each target adds ~3 credits."New value: +"Max targets to deep-map per account (1-20, default 5). Each target adds up to 3 credits."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, non-idempotent and non-destructive, so the safety profile is largely covered structurally. The description adds genuinely useful non-annotation context: worst-case credit reservation (balance must cover 1 + 3 × max_targets), that only actual spend is charged and reported, and the meaning of the three pool types. It does not explain what server-side state changes justify readOnlyHint=false (credits? a persisted queue?), leaving a gap against the annotations.

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?

One dense paragraph, front-loaded with the credit cost bracket and the core verb, then moving to response shape, pool semantics, and pricing rationale. Every clause carries load, but the credit explanation is repeated (bracket up front and again at the end), making it slightly heavier than necessary.

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?

With no output schema, the description properly compensates by enumerating the returned targets fields (target_id, person_id, full_name, current_title, linkedin_url) and the _meta.next_step(s) chaining guidance. Combined with cost bounds, pool definitions, and the single required parameter, an agent has enough to call it correctly and interpret the result.

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 coverage is 100%, so baseline is 3; the description goes beyond it by attaching concrete cost math to max_targets (7 credits at 2, 16 at the default 5, 61 at 20). It also names the returned target fields and the meaning of title_keywords-derived pools, which helps an agent reason about parameter effects rather than just types.

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?

Opens with a specific verb+resource ("Map the professional graph around a target company") and then states the concrete pipeline it executes: find senior decision-makers, pull targets' posts/reactions/comments to identify engagers, score connections, produce a prioritized outreach queue. It distinguishes itself from the siblings it names (get_outreach_queue, get_outreach_path) so an agent can tell what this tool uniquely produces without reading 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 Guidelines4/5

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

Gives clear when-to-use context: this is the entry point that produces targets, get_outreach_queue is the scored queue, and get_outreach_path is the free follow-up. It also positions itself against linkedin_people_search by noting the bundled lead search is a deliberate 1-credit discount versus 5 credits per page. It never states an explicit exclusion (e.g., when to skip mapping and call get_outreach_queue directly), so it falls just short of full when/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