Skip to main content
Glama

Count Mentions

count_mentions
Read-onlyIdempotent

Counts mentions that match selected filters and returns only the total, not rows, so you can size dashboards or triage batches and decide whether paging is worthwhile.

Instructions

Count mentions matching the same filters as list_mentions, returning { total } and no rows. The same defaults apply: REJECTED excluded unless statuses includes it, and scores below the website's minimum (30 by default) hidden unless includeLowRelevance is true. Use it for dashboards, to size a triage batch, or to decide whether paging list_mentions is worthwhile; list_mentions already returns total with its rows, so skip this when you fetch rows anyway. Takes no sort, limit, or offset.

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": "count_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly mentions RedReplier saved at or before this ISO 8601 datetime (ingestion time, not the post date). Omit for no upper bound
fromNoOnly mentions RedReplier saved at or after this ISO 8601 datetime (ingestion time, not the post date). Omit for no lower bound
sourcesNoWhich networks the conversations come from. Reddit splits into posts and comments, TWITTER is X, FACEBOOK is public pages and profiles, and FACEBOOK_GROUP is posts inside Facebook groups. Omit for every network
keywordsNoKeyword texts whose mentions to count: the value field of a keyword in list_websites or get_website, not its id. Each must match the whole keyword, ignoring case. Omit for every keyword
minScoreNoRelevance score a mention needs to be included, e.g. 70 for strong leads only. Setting it also drops mentions that have no score yet. It adds to the website's own minimum score rather than replacing it, so pair it with includeLowRelevance to look below that. Omit for no extra cutoff
statusesNoWhich triage states to include. NEW means nobody has reviewed the mention yet, APPROVED means someone marked it a real lead, REJECTED means someone marked it noise. Omit to see new and approved mentions; rejected ones show only when you ask for them
websiteIdNoWebsite whose mentions to read, by its id from list_websites. Omit to cover every website in the workspace
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another
scoreBucketsNoScore bands to include, combined with OR. Each band covers a range of the 0-100 relevance score: VERY_LOW under 10, LOW 10-29, MEDIUM 30-49, HIGH 50-74, VERY_HIGH 75 and up. Omit for every band. The two lowest bands return rows only with includeLowRelevance set
includeLowRelevanceNoAlso include mentions scoring below the website's minimum score (30 by default). Omit or false to hide them

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / from / description
      Previous value: -"Only mentions ingested at/after this ISO 8601 datetime"New value: +"Only mentions RedReplier saved at or after this ISO 8601 datetime (ingestion time, not the post date). Omit for no lower bound"
    • changedInput schema / properties / includeLowRelevance / description
      Previous value: -"Include mentions below the website minimum score (30 by default), hidden otherwise"New value: +"Also include mentions scoring below the website's minimum score (30 by default). Omit or false to hide them"
    • changedInput schema / properties / keywords / description
      Previous value: -"Count only mentions matched by these keyword values (case-insensitive exact match)"New value: +"Keyword texts whose mentions to count: the value field of a keyword in list_websites or get_website, not its id. Each must match the whole keyword, ignoring case. Omit for every keyword"
    • addedInput schema / properties / minScore
      Added value: +{
      +  "description": "Relevance score a mention needs to be included, e.g. 70 for strong leads only. Setting it also drops mentions that have no score yet. It adds to the website's own minimum score rather than replacing it, so pair it with includeLowRelevance to look below that. Omit for no extra cutoff",
      +  "maximum": 100,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / scoreBuckets / description
      Previous value: -"Relevance buckets, OR-combined: VERY_LOW (<10), LOW (10-29), MEDIUM (30-49), HIGH (50-74), VERY_HIGH (75+). LOW and VERY_LOW only count when includeLowRelevance is also true"New value: +"Score bands to include, combined with OR. Each band covers a range of the 0-100 relevance score: VERY_LOW under 10, LOW 10-29, MEDIUM 30-49, HIGH 50-74, VERY_HIGH 75 and up. Omit for every band. The two lowest bands return rows only with includeLowRelevance set"
    • changedInput schema / properties / sources / description
      Previous value: -"Filter by source: REDDIT_POST, REDDIT_COMMENT, TWITTER (X), BLUESKY, HACKERNEWS"New value: +"Which networks the conversations come from. Reddit splits into posts and comments, TWITTER is X, FACEBOOK is public pages and profiles, and FACEBOOK_GROUP is posts inside Facebook groups. Omit for every network"
    • changedInput schema / properties / sources / items / enum
      Previous value: -[
      -  "REDDIT_POST",
      -  "REDDIT_COMMENT",
      -  "TWITTER",
      -  "BLUESKY",
      -  "HACKERNEWS"
      -]New value: +[
      +  "REDDIT_POST",
      +  "REDDIT_COMMENT",
      +  "TWITTER",
      +  "BLUESKY",
      +  "HACKERNEWS",
      +  "FACEBOOK",
      +  "FACEBOOK_GROUP"
      +]
    • changedInput schema / properties / statuses / description
      Previous value: -"Filter by status (NEW, APPROVED, REJECTED); omit to count everything except REJECTED"New value: +"Which triage states to include. NEW means nobody has reviewed the mention yet, APPROVED means someone marked it a real lead, REJECTED means someone marked it noise. Omit to see new and approved mentions; rejected ones show only when you ask for them"
    • changedInput schema / properties / to / description
      Previous value: -"Only mentions ingested at/before this ISO 8601 datetime"New value: +"Only mentions RedReplier saved at or before this ISO 8601 datetime (ingestion time, not the post date). Omit for no upper bound"
    • changedInput schema / properties / websiteId / description
      Previous value: -"Filter to one website (UUID)"New value: +"Website whose mentions to read, by its id from list_websites. Omit to cover every website in the workspace"
    • addedInput schema / properties / websiteId / format
      Added value: +"uuid"
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
      +  "type": "string"
      +}
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • removedOutput schema / properties / result / description
      Removed value: -"{ total }: the number of mentions matching the filters after the default exclusions."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "total": {
      +    "description": "Mentions matching the filters after the default exclusions",
      +    "type": "integer"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "total"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed8 schema fields changedv0.1.1
    • changedInput schema / properties / from / description
      Previous value: -"ISO 8601 datetime"New value: +"Only mentions ingested at/after this ISO 8601 datetime"
    • addedInput schema / properties / includeLowRelevance / description
      Added value: +"Include mentions below the website minimum score (30 by default), hidden otherwise"
    • addedInput schema / properties / keywords / description
      Added value: +"Count only mentions matched by these keyword values (case-insensitive exact match)"
    • addedInput schema / properties / scoreBuckets / description
      Added value: +"Relevance buckets, OR-combined: VERY_LOW (<10), LOW (10-29), MEDIUM (30-49), HIGH (50-74), VERY_HIGH (75+). LOW and VERY_LOW only count when includeLowRelevance is also true"
    • addedInput schema / properties / sources / description
      Added value: +"Filter by source: REDDIT_POST, REDDIT_COMMENT, TWITTER (X), BLUESKY, HACKERNEWS"
    • addedInput schema / properties / statuses / description
      Added value: +"Filter by status (NEW, APPROVED, REJECTED); omit to count everything except REJECTED"
    • changedInput schema / properties / to / description
      Previous value: -"ISO 8601 datetime"New value: +"Only mentions ingested at/before this ISO 8601 datetime"
    • changedOutput schema / properties / result / description
      Previous value: -"The number of mentions matching the given filters."New value: +"{ total }: the number of mentions matching the filters after the default exclusions."
  3. First observedv0.1.0

TDQS

A4.5/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, non-destructive, closed-world), yet the description adds real behavioral context the annotations do not: REJECTED is excluded by default, mentions below the website minimum (30 by default) are hidden unless includeLowRelevance is set, and pagination parameters are not supported. It stops short of describing performance or result-size characteristics for large workspaces, which keeps it below a 5.

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?

Four sentences, front-loaded with purpose and return shape, then defaults, then usage guidance, then a constraint. Nothing is redundant and no sentence could be dropped without losing 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?

Output schema exists, and the description still states the return shape briefly. For a zero-required-parameter read tool with fully documented filters, the agent has everything needed to decide and invoke correctly.

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% and the parameter docs are unusually rich, so the baseline is 3. The description restates the default semantics for statuses and includeLowRelevance that the schema already documents, adding confirmation rather than new meaning.

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?

Names a specific verb (count) and resource (mentions) and immediately ties it to list_mentions's filter set while stating the return shape ({ total }, no rows). An agent can distinguish it from list_mentions from the first clause alone.

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 concrete positive cases (dashboards, sizing a triage batch, deciding whether paging is worthwhile) and an explicit exclusion: skip it when you are fetching rows anyway because list_mentions already returns total. It also rules out sort/limit/offset, so the agent knows what cannot be done.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.