Skip to main content
Glama

Engagers Grouped by Company

get_post_engagers_by_company
Read-onlyIdempotent

[Read · free] Given a LinkedIn post URL or id, return the companies whose people engaged (reacted/commented), ranked by engager count. Joins through person_positions(is_current=true). Pure DB read — no LinkedIn pull, no credits charged. Engagers without a known current company are bucketed as _unknown_company. Optional industry_urn filter narrows to one industry.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax companies to return (1-100, default 20)
post_idNoposts.id UUID (use when you already know the local id)
post_urlNoPublic LinkedIn post URL (e.g. https://www.linkedin.com/feed/update/urn:li:activity:1234)
industry_urnNoOptional urn:li:fsd_industry:<id> filter (from companies.industry_urn)
top_engagers_per_companyNoHow many sample engager names to attach per company row (0-10, default 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (which already declare readOnly/idempotent/non-destructive), the description discloses the query semantics: a join through person_positions filtered to is_current=true, and the bucketing of unmatched engagers under `_unknown_company`. It also confirms no credits are consumed, which the annotations cannot express. This is exactly the kind of behavioral context that earns full marks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with a cost/read tag, then the operation, then the join mechanics and edge case. Every clause carries information the agent cannot get from the structured fields; nothing is repeated filler.

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 must convey the return shape, and it does explain the ordering dimension (engager count) and the unknown-company bucket. It stops short of describing the row fields a caller actually receives, notably the sample engager names driven by top_engagers_per_company, leaving part of the response contract implicit.

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%, so every parameter including post_id vs post_url and the limit bounds is already documented. The description adds only one marginal clarification, that industry_urn narrows results to a single industry. It neither explains the post_id/post_url precedence for the caller nor elaborates on top_engagers_per_company beyond what the schema says.

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

Purpose4/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 companies whose people engaged on a given post, ranked by engager count. The scope (post URL or id in, company rollup out) is unambiguous and takes no effort to parse. It never names an alternative such as get_post_set_engagers or get_alumni_engagers, so the agent gets no explicit sibling differentiation.

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

Usage Guidelines3/5

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

"Given a LinkedIn post URL or id" establishes the input situation, and "Pure DB read — no LinkedIn pull, no credits charged" tells the agent this is a cheap operation. However, there is no statement of when to prefer this over the other engager-oriented siblings, and no exclusions or prerequisites. Usage is implied rather than guided.

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