Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Manually trigger a monitor poll

monitors_trigger

Queues an immediate check for an active social media monitor and returns once the check is queued, not when it finishes.

Instructions

Queue an immediate check for an active monitor (async — returns once queued, not once the check finishes).

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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "monitors_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Adds real value beyond the annotations by disclosing async semantics — the call returns once the check is queued, not when it completes — which no structured field conveys. Annotations already cover safety (readOnly=false, destructive=false, idempotent=false), so this is useful supplementary context rather than carrying the full burden.

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?

One front-loaded sentence with the async caveat in parentheses; no wasted words and the most important operational detail (returns on queue, not completion) is stated immediately.

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?

For a fire-and-forget trigger tool with no output schema, the async contract and active-monitor precondition cover the essentials an agent needs. Minor gaps remain around what happens on an inactive or invalid monitor.

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 coverage is 75% and the schema documents context, llm_model, and conversation_id in detail; the description adds nothing about parameters, only referencing the monitor implicitly. Baseline 3 is appropriate given the high schema coverage.

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 ("Queue an immediate check for an active monitor"), which is clearly distinct from listing checks or fetching monitor details. It does not explicitly name the sibling it replaces, but the action is unambiguous.

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 qualifier "active monitor" implies a precondition (the monitor must be enabled), giving implied usage guidance, but the description never states when to trigger manually versus waiting for the scheduled poll, nor what happens for inactive monitors.

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

Deploy Server

Other Tools