Skip to main content
Glama

RedReplier

by com.redreplier
OverviewDiscussionsAdmin

Count Mentions

count_mentions
Read-only

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoOnly mentions ingested at/before this ISO 8601 datetime
fromNoOnly mentions ingested at/after this ISO 8601 datetime
sourcesNoFilter by source: REDDIT_POST, REDDIT_COMMENT, TWITTER (X), BLUESKY, HACKERNEWS, FACEBOOK (posts outside groups), FACEBOOK_GROUP (posts in Facebook groups)
keywordsNoCount only mentions matched by these keyword values (case-insensitive exact match)
minScoreNoOnly mentions scoring at least this (0-100); unscored mentions are left out. Stacks on the website minimum, so set includeLowRelevance to go below it
statusesNoFilter by status (NEW, APPROVED, REJECTED); omit to count everything except REJECTED
websiteIdNoFilter to one website (UUID)
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
scoreBucketsNoRelevance 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
includeLowRelevanceNoInclude mentions below the website minimum score (30 by default), hidden otherwise

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo{ total }: the number of mentions matching the filters after the default exclusions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed2 schema fields changed
    • changedInput schema / properties / sources / description
      Previous value: -"Filter by source: REDDIT_POST, REDDIT_COMMENT, TWITTER (X), BLUESKY, HACKERNEWS"New value: +"Filter by source: REDDIT_POST, REDDIT_COMMENT, TWITTER (X), BLUESKY, HACKERNEWS, FACEBOOK (posts outside groups), FACEBOOK_GROUP (posts in Facebook groups)"
    • 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"
+]
  3. Changed2 schema fields changed
    • addedInput schema / properties / minScore
      Added value: +{
+  "description": "Only mentions scoring at least this (0-100); unscored mentions are left out. Stacks on the website minimum, so set includeLowRelevance to go below it",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}
    • 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"
+}
  4. Changed8 schema fields changed
    • 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."
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, non-destructive, and closed-world behavior. The description adds important default-filtering behavior: REJECTED is excluded unless statuses includes it, low-score mentions are hidden unless includeLowRelevance is true, and sort/limit/offset are not accepted.

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?

Front-loaded with the core action and return shape, then defaults, then usage guidance. Every sentence contributes useful routing or filtering information, and there is no filler.

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 ten-parameter read tool with an output schema, this is complete. It explains the return shape, default exclusions, relevance filtering, sibling relationship, and the absence of pagination controls, leaving no material gotcha for an agent to discover.

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 ten parameters are already documented in the schema. The description reinforces default semantics for statuses and includeLowRelevance and notes the absence of sort/limit/offset, but adds little parameter-level syntax beyond what the schema provides.

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: counting mentions. It immediately distinguishes itself from the sibling list_mentions by explaining that it returns only { total } and no rows, so an agent can tell the two apart without opening either 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?

Explicitly names when to use it (dashboards, sizing a triage batch, deciding whether paging list_mentions is worthwhile) and when to skip it (when you are already fetching rows via list_mentions). It routes the agent between alternatives with a clear condition.

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

All RedReplier toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources