Skip to main content
Glama

Get Inbound Attribution

get_inbound_attribution
Read-onlyIdempotent

[Read · free] Which of your posts bring in DMs, leads and clients, next to which get engagement. Reads the inbound outcomes logged with log_outcome (inbound_dm | lead | client) for one of your tracked profiles over the last days (default 90). Returns totals, top_by_outcomes (posts credited with at least one outcome), top_by_engagement (your most-engaged posts in the window, with their outcome counts, so the two rankings can be compared), by_format, and the unattributed outcomes still waiting for a post (fix with log_outcome outcome_id + post_url). Engagement is not used to attribute: outcomes are matched by post_url, message text and timing. Free — costs 0 credits.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "get_inbound_attribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days (default 90)
profile_idYesYour tracked profile id from list_profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description usefully adds that the call is free/0 credits and, importantly, the attribution method ('outcomes are matched by post_url, message text and timing' and 'Engagement is not used to attribute'). That methodological disclosure is genuine value beyond the annotations, but the safety profile itself is entirely annotation-supplied, so a 3 rather than higher.

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?

Purpose is front-loaded in the opening sentence, followed by data source, return shape, methodology, and cost in a logical order. Slightly dense and mildly redundant on cost ('[Read · free]' in the lead and 'Free — costs 0 credits' at the end), but no sentence is wasted.

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?

There is no output schema, and the description compensates by enumerating the return keys (totals, top_by_outcomes, top_by_engagement, by_format, unattributed outcomes) and explaining what each ranking means. For a two-parameter read tool that is complete enough to invoke and interpret correctly without further documentation.

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 100% — both profile_id and days are documented with units and the 90-day default — so the schema already does the heavy lifting. The description restates the default window and adds the mild hint that profile_id is a tracked profile, but contributes no new syntax or format detail; baseline 3 applies.

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 ('Which of your posts bring in DMs, leads and clients') plus the contrast with engagement, so the agent can distinguish it from get_posts or get_campaign_stats without reading a schema. The framing 'next to which get engagement' makes the two-part purpose unmistakable.

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?

Clearly establishes prerequisites and context: it reads outcomes logged with log_outcome, scoped to one tracked profile and a look-back window, and names the remediation path ('fix with log_outcome outcome_id + post_url') for unattributed results. It stops short of explicit when-not-to-use guidance or naming an alternative for a pure-engagement view, so not a 5.

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.