Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List monitor events

monitors_events_list
Read-onlyIdempotent

List and retrieve events for a specific monitor via a pull API, letting you review event data even when webhooks are not configured.

Instructions

Pull API for a monitor's events — queryable regardless of webhook delivery configuration.

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_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
cursorNo
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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact — results are available even when webhooks are not delivered — but says nothing about pagination behavior, result ordering, or retention window, which matters for a cursor-based list.

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?

A single front-loaded sentence with no filler and no restating of the title. It is efficient, though its brevity is part of why other dimensions are thin — slightly more would have earned its place here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, three-required paginated endpoint with no output schema and a non-obvious conversation_id handshake protocol, the description covers almost none of what an agent needs. It never explains pagination via cursor, what an 'event' object contains, or how the required context/llm_model fields relate to the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: context, llm_model and conversation_id are documented in the schema, while id, limit and cursor are undocumented in both places. The description contributes only the implied mapping of 'a monitor's events' to the id parameter and nothing about cursor paging or the limit cap, so it fails to compensate for the uncovered parameters.

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: retrieve a monitor's events, and clarifies they are the raw API events rather than aggregated results. It is clear on its own, but gives no hint of how it differs from close siblings such as monitors_checks_list or monitors_sources_list, leaving the agent to guess which 'monitor' sub-list it wants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is the clause 'queryable regardless of webhook delivery configuration', which weakly implies polling/backfill use cases. There is no explicit when-to-use, when-not-to-use, or pointer to the sibling tools for checks, sources, or monitor metadata, so selection among the many *_list siblings is left entirely to inference.

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