Skip to main content
Glama

Alumni / Coworker Engagers for a Company

get_alumni_engagers
Read-onlyIdempotent

[Read · free] Given a company (company_url, LinkedIn's numeric linkedin_company_id as linkedin_company_info returns it, an exact company_name, or a companies.id UUID), return engagers (across your collected posts) who have a position at that company. Relation filter: 'coworker' = current employees, 'alumni' = any past or current position (most useful for page_type='SCHOOL' companies), 'any' = both. Matches need job history on file, and engagers collected from reactions/comments usually have none: coverage counts candidates (engagers whose headline or current company names the company) with and without job history, and when missing data may hide matches _meta.next_step names enrich_people with the exact person_ids to pass and its credit cost. The company must be saved in Flux: if it is not, the error's _meta.next_step names linkedin_company_info (1 credit) with the arguments that save it; a company_name that matches several saved companies returns candidates to pick from instead of guessing. Pure DB read — no LinkedIn pull, no credits charged.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax engagers to return (1-100, default 20)
relationNocoworker = current employees only; alumni = any position (past or current); any = bothany
company_idNocompanies.id UUID
company_urlNoPublic LinkedIn company URL
company_nameNoExact company name, case-insensitive. Several matches return candidates.
linkedin_company_idNoLinkedIn's numeric company id (the `id` linkedin_company_info returns)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / company_name
      Added value: +{
      +  "description": "Exact company name, case-insensitive. Several matches return candidates.",
      +  "type": "string"
      +}
    • addedInput schema / properties / linkedin_company_id
      Added value: +{
      +  "description": "LinkedIn's numeric company id (the `id` linkedin_company_info returns)",
      +  "type": [
      +    "string",
      +    "number"
      +  ]
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the bar is lower; the description nonetheless adds valuable behavior: no LinkedIn pull and no credits charged, matching requires job history on file, and `coverage` counts candidates with and without history. The `_meta.next_step` failure/recovery path is disclosed rather than left to discovery.

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 '[Read · free]' marker and the primary input forms, then proceeds to filters, coverage caveats, and error routing. It is dense and long for a single paragraph, but nearly every clause carries actionable information; minor redundancy with the schema's enum descriptions.

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?

For a six-parameter read tool with no output schema, the description covers the return shape (`coverage`, `candidates`, `_meta.next_step`), the failure/recovery paths, and credit implications. Nothing an agent needs to call it correctly or interpret a partial result is missing.

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 coverage is 100%, so all six parameters are already documented with descriptions and enum meanings. The description restates the accepted company identifier forms (URL, numeric LinkedIn id, exact name, UUID) and relation semantics, adding reinforcement but little syntax beyond the schema; baseline 3 applies.

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 engagers with a position at a given company, across collected posts. The company-wide scope is clear, but no sibling tool (e.g. get_post_engagers_by_company or get_company_engagement_overlap) is named to draw an explicit boundary, so an agent must infer which engager tool to pick.

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

Usage Guidelines5/5

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

Gives explicit conditional guidance: the relation enum is explained with a recommended case ('alumni' for page_type='SCHOOL'), missing-data situations route to enrich_people with exact args and credit cost, and an unsaved company routes to linkedin_company_info (1 credit) with the arguments that save it. Ambiguous names return candidates rather than guessing.

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