Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Update a monitor

monitors_update

Modify a social media monitor's name, schedule, webhook endpoint, spend cap, or active/paused status to keep tracking aligned with your goals.

Instructions

Update a monitor's name, schedule, webhook endpoint, spend cap, or status (pause/resume).

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

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
typeNo
statusNo
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
minutesNo
timezoneNo
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.
expressionNo
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds the list of mutable fields but omits the important mutation semantics: whether this is a merge/partial update, what happens to omitted fields, and how null values (e.g. spendCapCredits, webhookEndpointId) behave.

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?

A single compact sentence that front-loads the verb and resource and lists the mutable fields without redundant wording. Nothing here is filler.

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 12-parameter mutation tool with 25% schema coverage and no output schema, the description is too thin. It says nothing about the mandatory context/llm_model/conversation_id parameters, partial-update behavior, null-clearing semantics, or what a successful update returns.

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?

With only 25% schema coverage across 12 parameters, the description does partially compensate by mapping concepts to fields (schedule, spend cap, webhook endpoint, status). However, it does not explain the interval-vs-cron pairing (minutes vs expression/timezone), the required meta-parameters (context, llm_model, conversation_id), or the meaning of nullable fields.

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 names a specific verb (update) and resource (monitor) and enumerates the mutable fields: name, schedule, webhook endpoint, spend cap, status. That is enough to separate it from monitors_create and monitors_delete, though it never explicitly names a sibling as the alternative.

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 only implied — that an existing monitor identified by 'id' must already exist, and that pausing/resuming is done through the status field. There is no explicit when-to-use, when-not-to-use, or guidance on partial versus full updates, leaving the agent to infer behavior.

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