Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Create a monitor

monitors_create

Create a watch on a social account or search and receive a signed webhook when new content appears; the initial response baselines current items.

Instructions

Watch a social account or search and get a signed webhook when new content appears. Runs a synchronous baseline check on create — the response includes what's there right now, and you'll only get webhooks for items after that.

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": {
      "operationId": "<operationId>",
      "params": "<params>",
      "type": "<type>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "monitors_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
typeYesinterval or cron.
paramsYesParams for the source, e.g. { handle: "elonmusk" }.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
minutesNoRequired when type is interval.
timezoneNoIANA timezone, required when type is cron.
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.
expressionNoCron expression, required when type is cron.
operationIdYesA watchable operationId from monitors_sources_list.
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.
spendCapCreditsNo
webhookEndpointIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world creation with no destructive effect. The description adds genuinely non-obvious behavior: a synchronous baseline check runs at creation time, the response reflects current content, and only items appearing after creation generate webhooks. It omits the conversation_id handshake and webhook endpoint requirement, which live only in the schema.

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?

Two tight sentences with zero filler; the core capability comes first and the baseline-check caveat, the most surprising detail, follows immediately.

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

Completeness3/5

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

With 12 parameters, 5 required, nested params, and no output schema, the definition should do more to explain the required fields and the two-phase conversation_id/webhookEndpointId setup. The description partially compensates by explaining what the creation response contains, but an agent could still fail to assemble a valid call from the description alone.

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 a fairly high 75%, and the schema already explains interval vs cron, required minutes/expression/timezone, params, and the conversation_id echo rule. The description adds no parameter-level meaning beyond that, which is acceptable at this coverage level but leaves the baseline at 3.

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 states a specific verb and resource: it watches a social account or search and delivers a signed webhook on new content, which is far more concrete than the title 'Create a monitor'. It does not name or contrast with siblings such as monitors_trigger or monitors_update, so an agent must infer the boundary from the verb alone.

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?

Usage is implied by the watching/webhook framing, but there is no explicit when-to-use versus monitors_trigger, nor are prerequisites such as obtaining a valid operationId from monitors_sources_list or setting up a webhook endpoint mentioned in the description. The agent gets the gist but must consult the schema for the operational conditions.

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