Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Update a saved query

saved_queries_update

Update an existing saved query's name, Boolean wording, platforms, schedule, alerts, webhook, briefing, noise presets, sentiment/insights, or active status to refine what it monitors.

Instructions

Change a saved query: its name, query, platforms, schedule, limits, volume alert (alertThreshold, null to remove it), webhook endpoint, briefing, noise presets, platformSearches (null to search every platform as planned), sentiment or insights (null to turn them off) (only the fields given), or pause or resume it with status. A new query wording is saved as a new version; matches already stored keep the version that found them.

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": "saved_queries_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe saved query's id.
nameNoA name for the query, shown in the dashboard and in alerts.
noiseNoKinds of post its runs leave out: `jobs` (job ads and job seekers' posts), `giveaways` (giveaway and contest entry posts), `crypto-spam` (crypto promotion and money scams). Checked on each post after it's found, so a run costs the same. Empty, the default, leaves everything in.
queryNoThe Boolean query. Check it for free first with POST /v1/query/validate.
statusNoPause or resume it. Resuming a `capped` or `broken` query tries again.
syntaxNoSyntax the query is written in: `native` (Social Fetch's Boolean language), or another tool's to import: `x` (X search), `onclusive`, `talkwalker`, `brandwatch` (also Cision Social Listening) or `meltwater`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
briefingNoA briefing on what it found: `daily` covers the day before (UTC) and comes at 08:00 UTC; `weekly` covers Monday to Sunday and comes on Monday at 08:00 UTC. It counts the posts, the change on the period before, the stories, each platform's posts, the loudest voices and the 5 most engaged posts, is shown on the query in the Listening app, and is sent to its webhook endpoint as the `saved_query.briefing` event. Only for an active query that ran in the period without failing. Null for none, the default.
insightsNo
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.
platformsNoPlatforms to search. Empty means every platform search covers.
sentimentNoGive each new match a sentiment estimate (positive, neutral or negative), for 1 credit per 10 matches given one, on top of each run's maxCreditsPerRun but within monthlyCreditCap when one is set. Only matches given one are charged. A match keeps its sentiment: it's never estimated or charged again. Default false.
alertThresholdNoA volume alert: when a run brings the posts it found in the trailing `window` to at least `posts`, it sends the `saved_query.threshold` webhook event, at most once a window. The first run of a query or of a new wording doesn't alert (it finds the backlog). Null for none.
cadenceMinutesNoMinutes between scheduled runs, from 15 to 10080 (a week).
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.
maxCreditsPerRunNoThe most one run may charge, held while it runs as with POST /v1/query/search; what isn't used is given back.
monthlyCreditCapNoThe most all its runs may charge in a calendar month (UTC). Null for no cap beyond each run's.
platformSearchesNo
webhookEndpointIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: a new query wording creates a new version, and already-stored matches retain the version that found them, which matters for a caller reasoning about history. It also documents null semantics per field (null removes the alert, null restores planned platform searches, null disables sentiment/insights). It does not say what is returned or what happens on an unknown/invalid id, and the annotations already cover the safety profile (readOnly false, destructive false, idempotent false).

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?

Front-loaded with the verb and the field inventory, and essentially every clause carries information (field name plus null/version semantics). It is a single very dense sentence, however, which makes it harder to scan than a short bulleted field list would be.

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 19-parameter mutation tool with no output schema and no destructive flag, the description does a solid job covering partial-update semantics, null semantics, and versioning side effects. Gaps remain around the response shape, error behavior on a bad id, and how updates interact with a currently running schedule, plus undescribed parameters like webhookEndpointId null.

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

Parameters4/5

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

With 84% schema coverage the baseline is 3, and the description earns above that by explaining null behavior on alertThreshold, platformSearches, sentiment and insights in a way that is not repeated in the schema. It still omits meaning for several parameters (syntax, cadenceMinutes, maxCreditsPerRun, monthlyCreditCap, webhookEndpointId, context), leaving them entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Change a saved query") and then enumerates the mutable field groups — name, query, platforms, schedule, limits, alert, webhook, briefing, noise, platformSearches, sentiment, insights, status. An agent can distinguish this from saved_queries_create, saved_queries_run and saved_queries_get from the description 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?

The partial-update contract is stated ("only the fields given") and the pause/resume path via `status` is called out, which implies when this tool is appropriate. But there is no explicit routing to alternatives — nothing like "to create, use saved_queries_create" or "to validate a query first, use query_validate_post" — so an agent must infer the boundary.

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