Skip to main content
Glama

Get Post-Set Engagers

get_post_set_engagers

[Acquire · 1 credit/page + 3/person enriched] Pull from LinkedIn (costs credits) and return the consolidated, deduped people who reacted to or commented on a SET of posts — one tracked profile's posts (profile_id), a post collection (collection_id), or an explicit list of up to 50 posts (post_ids and/or post_urls, e.g. the post_ids linkedin_post_search returns; a URL not yet in Flux is stubbed for free, no save_post needed). Fetches only posts not synced within freshness_days, walks up to max_pages_per_post pages (100 people/page) of reactions and of comments per post, includes comment replies, and enriches (title/company via a profile lookup) only never-seen people, up to max_enrich. Costs 1 credit per page fetched (a page is up to 100 people; a post with under 100 reactions and under 100 comments = 2 credits; the most a post can cost is 2 × max_pages_per_post) + 3 per person enriched; cached posts and cached pages are free. The balance must cover the worst case (posts × 2 × max_pages_per_post + max_enrich × 3) before anything runs (get_cost_estimate with these params returns the same number); you are charged only for pages actually fetched. When the balance is short, the insufficient_credits error spells out what the worst case assumed and lists suggestions (smaller max_pages_per_post / max_posts / max_enrich, each with its resulting max) that fit the balance. Per-post reactions_fetched / reactions_total / comments_total / truncated tell you when a post had more engagers than were fetched.

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

Input Schema

NameRequiredDescriptionDefault
forceNoRe-sync posts even if within the freshness window
post_idsNoposts.id values (e.g. from linkedin_post_search results) — engagers across exactly these posts. Combine with post_urls; 50 total max. Each must be a post you can read.
max_postsNoMax posts to sync this call (1-100). Default 25; with post_ids/post_urls the default is the list length.
post_urlsNoLinkedIn post URLs — engagers across exactly these posts. URLs not yet in Flux get a stub row (no extra credit). Combine with post_ids; 50 total max.
max_enrichNoMax never-seen engagers to enrich via /linkedin/profile (0-100, default 0)
profile_idNoTracked profile id — engagers across this profile's stored posts
collection_idNopost_collections.id — engagers across this collection's posts
freshness_daysNoSkip posts whose engagers were synced within this many days
max_pages_per_postNoMax pages (100 people each) to walk per endpoint per post (1-20, default 10). Each page costs 1 credit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / max_posts / default
      Removed value: -25
    • changedInput schema / properties / max_posts / description
      Previous value: -"Max posts to sync this call (1-100)"New value: +"Max posts to sync this call (1-100). Default 25; with post_ids/post_urls the default is the list length."
    • addedInput schema / properties / post_ids
      Added value: +{
      +  "description": "posts.id values (e.g. from linkedin_post_search results) — engagers across exactly these posts. Combine with post_urls; 50 total max. Each must be a post you can read.",
      +  "items": {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
    • addedInput schema / properties / post_urls
      Added value: +{
      +  "description": "LinkedIn post URLs — engagers across exactly these posts. URLs not yet in Flux get a stub row (no extra credit). Combine with post_ids; 50 total max.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / max_pages_per_post
      Added value: +{
      +  "default": 10,
      +  "description": "Max pages (100 people each) to walk per endpoint per post (1-20, default 10). Each page costs 1 credit.",
      +  "maximum": 20,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, openWorldHint=true): it discloses the exact credit model (1/page + 3/enriched person), the worst-case balance formula, which pages/posts are free due to caching, and what the insufficient_credits error returns including a suggestions list. It also explains the per-post truncation signals, which is behavior nothing else in the definition surfaces.

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 action and cost tag before the mechanics, and nearly every clause carries a distinct fact. It is nonetheless one dense paragraph covering schema-adjacent detail, and the cost/pagination sentences would read faster as a short bulleted aside.

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?

No output schema exists, so the description carries return-value burden, and it does: it explains the consolidated/deduped people list plus per-post reactions_fetched/reactions_total/comments_total/truncated fields. For a 9-parameter, credit-spending, write-ish sync tool, an agent has enough to call it correctly and predict charges.

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?

Despite 100% schema coverage, the description adds meaning the schema cannot: the worst-case formula ties max_posts × max_pages_per_post × max_enrich together, and it explains that max_pages_per_post is per-endpoint-per-post and costs one credit per page. It also clarifies that post_urls for unknown posts are stubbed without extra credit.

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 the consolidated, deduped people who reacted to or commented on a SET of posts') and immediately scopes the three input modes (profile_id, collection_id, post_ids/post_urls). The 'SET of posts' framing separates it from single-post engager siblings without needing their names.

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 operational context: post_ids can come from linkedin_post_search, and post_urls need no save_post because unindexed URLs are stubbed free. It also points to get_cost_estimate as the way to preview the worst case. It does not explicitly say when to prefer this over the company- or alumni-scoped engager siblings, so the exclusions stop short of a full 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.

Resources