Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List a monitor's recent check history

monitors_checks_list
Read-onlyIdempotent

Lists the last ~50 monitor checks with outcome, credits, and reason so you can diagnose why a webhook was not delivered.

Instructions

The self-serve "why didn't I get a webhook" view — the last ~50 checks with outcome/credits/reason.

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

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.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds what the response contains (outcome, credits, reason) and that it is capped at roughly the last 50 checks with no pagination implied, which is genuine behavioral context. It does not explain ordering, staleness, or what the monitor id must refer to.

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 tightly packed sentence that front-loads the diagnostic use case and then the payload. The colloquial "self-serve" adds flavor rather than information, but nothing else is wasted.

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?

With no output schema, the description carries the burden of describing return values and does so reasonably: check count, outcome, credits and reason. What's missing is how the id is obtained and whether results are ordered or time-bounded, but for a simple read tool this is close to sufficient.

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%, with context, llm_model and conversation_id fully documented in the schema, so the baseline of 3 applies. The description adds only an indirect hint that the id identifies a monitor (via the title phrasing) and says nothing about the id's format or source.

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?

The description pairs a concrete resource (a monitor's last ~50 checks) with a diagnostic framing ("why didn't I get a webhook"), so the agent knows this is a check-history lookup rather than a monitor listing or event stream. It never states the verb explicitly and doesn't name how it differs from monitors_events_list or monitors_get, so it falls short of full sibling differentiation.

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 webhook-debugging framing implies when to reach for it, which is more than nothing but stops short of explicit guidance. It never says to prefer this over monitors_events_list for granular events, nor does it state prerequisites such as needing a monitor id from monitors_list.

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