Skip to main content
Glama

Engager Position History

get_engager_position_history
Read-onlyIdempotent

[Read · free] Return a person's full employment timeline from the position graph. Only for people connected to you: they engaged with posts you can see in Flux, are in one of your campaigns or segments, or you pulled them (an engagement pull, or their profile via linkedin_profile_info / linkedin_profile_posts). Anyone else returns not-found with a next_step to pull their profile via linkedin_profile_info. Sorted current-first, then most-recent past by started_at desc. 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_engager_position_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_idNopeople.id UUID
linkedin_urlNoPerson's LinkedIn profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, it discloses that this is a 'Pure DB read — no LinkedIn pull, no credits charged', which is the key cost/behavior distinction versus the profile-pull siblings. It also adds sort semantics (current-first, then started_at desc) and the not-found-with-next_step error behavior, none of which the annotations convey.

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?

The '[Read · free]' tag plus purpose are front-loaded, followed by eligibility, ordering, and cost. The middle sentence is dense but each clause maps to a distinct decision an agent must make; nothing is 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 should sketch the returned timeline, and it only implies fields via 'full employment timeline' and started_at sorting. It also leaves unresolved how the two optional identifiers combine or which one is preferred; otherwise it covers eligibility, cost, ordering, and error handling well.

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 'people.id UUID' and 'Person's LinkedIn profile URL' are already fully documented. The description adds no format or precedence guidance (e.g. what happens if both person_id and linkedin_url are supplied, or what happens if neither is supplied given zero required parameters).

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 first sentence gives a specific verb and resource: 'Return a person's full employment timeline from the position graph.' It explicitly contrasts with the sibling that does an actual LinkedIn pull (linkedin_profile_info), so an agent can distinguish this DB-read tool from the enrichment tools without opening a schema.

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?

It enumerates the exact eligibility conditions under which a person's history exists (engaged with posts you can see, in your campaigns/segments, or previously pulled), states the negative case (anyone else returns not-found with a next_step), and names the alternative to use in that case (linkedin_profile_info). This is explicit when-to-use and when-not-to-use guidance.

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