Skip to main content
Glama

Get Topic Insights

get_topic_insights
Read-onlyIdempotent

[Read · free] Surface the most-frequent topics in a profile's posts, with engagement context. Returns top N unigrams and (optionally) top N bigrams ranked by post count, each with avg_engagement, vs_baseline, and a sample_post_url. Mirrors the dashboard topics chart, server-side. Pass scope (a post_collections.id) to scope the analysis to a collection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_id": "<profile_id>"
    },
    "name": "get_topic_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoMax terms per list (default 15)
scopeNoOptional post_collections.id to scope the analysis
bigramsNoAlso compute and return top bigrams (default true)
date_toNoEnd date (ISO 8601)
date_fromNoStart date (ISO 8601)
profile_idYesTracked profile ID from list_profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds real context beyond them: it is free, computed server-side, mirrors the dashboard topics chart, and returns avg_engagement, vs_baseline and a sample_post_url per term. That is meaningful disclosure about cost and output shape. It does not mention limits such as rate caps or behaviour when a profile has too few posts.

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?

Three sentences, front-loaded with a '[Read · free]' tag and the core verb+resource, then output shape, then the scope hint. No filler. Slightly dense with parentheticals, but every clause carries information an agent can use.

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?

There is no output schema, and the description compensates by naming the returned fields (terms, avg_engagement, vs_baseline, sample_post_url) and the ranking basis. Combined with 100% schema coverage on inputs, an agent has enough to call this correctly. The main residual gap is the lack of guidance on sibling tools for adjacent insight queries.

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 all six parameters are already documented, making 3 the baseline. The description adds only modest meaning: that `n` applies to both the unigram and bigram lists and that `scope` narrows the whole analysis. It adds nothing on date_from/date_to semantics or how bigrams interact with n.

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: 'Surface the most-frequent topics in a profile's posts, with engagement context,' and elaborates that it returns top-N unigrams/bigrams ranked by post count. An agent can tell this is a topic-frequency analysis rather than a raw post fetch. It stops short of naming a sibling like get_posting_insights to differentiate itself explicitly.

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?

The only usage guidance is parameter-level: pass `scope` (a post_collections.id) to restrict the analysis to a collection. There is no statement of when to prefer this over get_posting_insights or other insight tools, and no when-not conditions. Usage is implied by the 'topics chart' framing rather than spelled out.

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