Skip to main content
Glama

Engagement Industry Breakdown

get_engagement_industry_breakdown
Read-onlyIdempotent

[Read · free] Histogram of engagers' companies grouped by industry. Pivots on companies.industry_hierarchy (e.g. 'Tech > Software Development'). Depth=1 buckets by top-level, =2 by top+mid, =3 by full hierarchy. Engagers with no current company / no industry hierarchy bucket as _unknown. Pure DB read — no LinkedIn pull, no credits charged. Needs engagers synced first: if the post(s) have no recorded engagements, run get_post_set_engagers (1 credit per page, works on a collection or profile) as the usual first step; linkedin_post_reactions / linkedin_post_comments (1 credit per page of up to 100 people, so usually 1 credit each) pull a single post.

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

Input Schema

NameRequiredDescriptionDefault
depthNo1=top-level industry, 2=mid, 3=leaf (full hierarchy)
post_idNoposts.id UUID
post_urlNoPublic LinkedIn post URL
sample_companies_per_bucketNoHow many sample company names to attach per industry row (0-10, default 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses that this is a pure DB read with no LinkedIn pull and no credits charged, and that engagers lacking a current company or industry hierarchy fall into an `_unknown` bucket. Those cost and data-completeness behaviors are exactly the kind of context an agent cannot infer from structured fields.

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 cost and read status, then purpose, then depth semantics, then prerequisites — a sensible ordering with no filler. The final sentence runs long and chains three sibling tools, but each clause carries actionable information.

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?

With no output schema, the description still characterizes the return shape (per-industry rows, sample company names per bucket, an `_unknown` row) and covers the cost model and data prerequisites. An agent has everything needed to decide and call correctly.

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 the schema already documents all four parameters and the baseline is 3. The description adds real meaning on top: the source field (companies.industry_hierarchy) with a format example, the three depth levels' bucketing behavior, and the `_unknown` fallback for missing industry data.

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: a histogram of engagers' companies grouped by industry, pivoted on companies.industry_hierarchy, and describes the depth-based bucketing that defines the result shape, so an agent can distinguish it from aggregate alternatives like get_post_engagers_by_company 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 Guidelines5/5

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

Gives an explicit prerequisite (engagers must be synced first), an explicit fallback condition ('if the post(s) have no recorded engagements'), and names the concrete alternative to run in that case (get_post_set_engagers), plus two single-post alternatives with their credit costs. This is genuine when/when-not routing rather than implied usage.

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