Skip to main content
Glama

Update Mention Status

update_mention_status
DestructiveIdempotent

Update a mention's triage status to approve it as a lead, reject it as noise, or return it to the inbox. Reversible, so you can correct any verdict later.

Instructions

Set one mention's triage status. APPROVED marks it a real lead; REJECTED marks it noise and drops it from default list_mentions and count_mentions results (pass statuses to see it again); NEW returns it to the inbox. Fully reversible: any status can move to any other; reviewedAt is set to the time of each APPROVED or REJECTED call and cleared on NEW. Judge on the content and relevanceScore, calling explain_mention first when the score looks off; never approve a mention you have not read. mentionId comes from list_mentions. Returns the updated mention.

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": {
      "mentionId": "<mentionId>",
      "status": "<status>"
    },
    "name": "update_mention_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesYour verdict on the mention. APPROVED records it as a real lead, REJECTED records it as noise and hides it from default lists, NEW puts it back to unreviewed
mentionIdYesID of the mention to triage, from list_mentions
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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / mentionId / description
      Previous value: -"Mention ID (UUID)"New value: +"ID of the mention to triage, from list_mentions"
    • addedInput schema / properties / mentionId / format
      Added value: +"uuid"
    • changedInput schema / properties / status / description
      Previous value: -"New status: APPROVED (real lead), REJECTED (noise, hidden from default lists), or NEW (back to inbox)"New value: +"Your verdict on the mention. APPROVED records it as a real lead, REJECTED records it as noise and hides it from default lists, NEW puts it back to unreviewed"
    • 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: -"The updated mention with its new status and reviewedAt (null when NEW)."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "aiReplySuggestion": {
      +    "description": "Draft reply for a human to review before posting; null until generated",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "author": {
      +    "description": "Author's public handle on that network",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "contentText": {
      +    "description": "Text of the post or comment",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "createdAt": {
      +    "description": "Record creation time, ISO 8601",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "id": {
      +    "description": "Mention ID for update_mention_status and explain_mention",
      +    "type": "string"
      +  },
      +  "ingestedAt": {
      +    "description": "When RedReplier saved it, ISO 8601; the from and to filters use this",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "keyword": {
      +    "description": "The monitored keyword this conversation matched",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "publishedAt": {
      +    "description": "When the author posted it, ISO 8601; null when the network gives no date",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "relevanceReason": {
      +    "description": "Why the scorer chose that score; null until generated",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "relevanceScore": {
      +    "description": "AI score from 0 to 100, higher means more worth a reply; null until scored",
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "reviewedAt": {
      +    "description": "When it was last set to APPROVED or REJECTED; null while NEW",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "source": {
      +    "description": "REDDIT_POST, REDDIT_COMMENT, TWITTER, BLUESKY, HACKERNEWS, FACEBOOK or FACEBOOK_GROUP",
      +    "type": "string"
      +  },
      +  "status": {
      +    "description": "Triage status: NEW, APPROVED or REJECTED",
      +    "type": "string"
      +  },
      +  "subreddit": {
      +    "description": "The subreddit on Reddit, the group id on FACEBOOK_GROUP, otherwise null",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "tags": {
      +    "description": "Tags the AI attached when explaining the mention",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "title": {
      +    "description": "Post title; null when the post has none",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "updatedAt": {
      +    "description": "Record update time, ISO 8601",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "url": {
      +    "description": "Link to the conversation; null when the platform gives no public link",
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "websiteId": {
      +    "description": "Website whose keyword matched",
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "id",
      +  "websiteId",
      +  "source",
      +  "keyword",
      +  "title",
      +  "contentText",
      +  "url",
      +  "author",
      +  "subreddit",
      +  "status",
      +  "relevanceScore",
      +  "relevanceReason",
      +  "aiReplySuggestion",
      +  "tags",
      +  "publishedAt",
      +  "ingestedAt",
      +  "reviewedAt",
      +  "createdAt",
      +  "updatedAt"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / status / description
      Previous value: -"New status: NEW, APPROVED, or REJECTED"New value: +"New status: APPROVED (real lead), REJECTED (noise, hidden from default lists), or NEW (back to inbox)"
    • changedOutput schema / properties / result / description
      Previous value: -"The mention with its updated status."New value: +"The updated mention with its new status and reviewedAt (null when NEW)."
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructive and idempotent annotations, the description explains the practical consequences of REJECTED: it hides the mention from default list_mentions and count_mentions results. It also discloses reversibility, the reviewedAt timestamp behavior on APPROVED/REJECTED, and that NEW clears that timestamp.

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 description is dense but front-loaded: purpose and status meanings come first, followed by operational guidance and reversibility details. Every sentence contributes actionable information without repetition.

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 three-parameter mutation tool with an output schema, the description covers the status semantics, reversal behavior, timestamp effects, ID sourcing, and review caution. The output schema handles the return value, so no further return-format detail is needed.

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 baseline is 3. The description still adds meaningful semantics beyond the schema by explaining downstream effects of each status on list and count results, and by tying reviewedAt changes to specific status transitions.

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 description opens with a specific verb and resource: 'Set one mention's triage status.' It immediately defines each status value's effect, so an agent can distinguish this tool from siblings like list_mentions or explain_mention 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?

It gives explicit decision guidance: judge on content and relevanceScore, call explain_mention first when the score looks off, never approve a mention you have not read, and source mentionId from list_mentions. It also explains how to retrieve rejected mentions again by passing statuses to list_mentions or count_mentions.

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