Skip to main content
Glama

Get Engagement Brief

get_engagement_brief
Read-onlyIdempotent

[Read · free] For one person, return their recent posts most relevant to what you post about — plus suggested talking points. Use before a warm comment or DM. Free — costs 0 credits.

Identify the person via exactly one of: target_id (a Constellation target — original input), person_id (a row in people), or linkedin_url (any form). The non-campaign forms work even when no Constellation campaign exists.

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_engagement_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_idNopeople.id — when you already have the canonical person row
target_idNoConstellation targets.id — for the original campaign-scoped flow
linkedin_urlNoLinkedIn profile URL (vanity or encoded form) — auto-resolved to a people row

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the call is free and costs 0 credits (a real constraint given a credits system with get_credit_balance siblings), and that linkedin_url is auto-resolved to a people row. Return shape is sketched but only loosely.

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-loaded with a tag and the core purpose in the first sentence, with the identifier-selection rule following. The 'Free — costs 0 credits' clause partly repeats the '[Read · free]' tag, a small redundancy, but overall the text is tight and well ordered.

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?

With no output schema, the description carries the burden of describing returns and does so at a high level (relevant recent posts plus suggested talking points). It covers identity resolution and cost, which are the main risks for this call. Only the volume/pagination of returned posts is left unstated.

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 stating the parameters are mutually exclusive ('exactly one of') and by explaining the lineage of each identifier — target_id is the original campaign-scoped input, person_id is a people row, linkedin_url is any form. That mutual-exclusivity rule is not stated in the schema itself, which makes this add real value.

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?

The description states a specific verb and resource ('return their recent posts most relevant to what you post about — plus suggested talking points') for a single person, and its framing ('engagement brief' for pre-outreach research) clearly separates it from sibling analytics tools like get_engagement_trends or get_profile_summary. An agent can tell it is a per-person relevance/prep tool without 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 Guidelines4/5

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

'Use before a warm comment or DM' gives an explicit usage context, and the closing line explains a conditional availability rule (non-campaign forms work even when no Constellation campaign exists). What is missing is naming a sibling alternative for when the agent wants a different kind of brief, so it stops short of full when/when-not routing.

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