Skip to main content
Glama

smry Product

by ai.smry.r
OverviewDiscussionsAdmin

Selector-based writes with dry-run preview

mutate_feeds
Destructive

Preview changes to matching sources, entries, or collections. Default dry_run:true returns would_affect, sample, and commit_token without changing them. Commit by sending the same op and commit_token; retries replay the recorded result. Explicit dry_run:false applies immediately. sources.move needs set.collection; sources.rename needs set.title; collections.create/rename need set.name. Collections rename/delete need exactly one where.collection. Use manage_collections for direct collection CRUD. Check partial and each outcome after committing. Example: {"op":"collections.create","set":{"name":"Research"}} Example: {"op":"sources.move","where":{"source":{"include":[42]}},"set":{"collection":"Research"}} Example: {"op":"sources.move","commit_token":""}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYessources.* use where.source or where.collection, never entry filters. entries.* use the full where predicate. collections.rename/delete select one where.collection; collections.create uses set.name.
setNo
whereNoEntry selection predicate: fields AND together; omit a field to not filter on it. Source queries/mutations accept only collection and source; use query having for source-health filters.
dry_runNoDefault true: preview affected records and return a commit_token. Explicit false applies immediately; prefer preview then commit_token for agent workflows.
commit_tokenNoFrom a dry run. Single-use and idempotent: resending after a network failure replays the recorded outcome.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / where / properties / discovered_after / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"When smry first saw the entry. Backfill makes old posts look new here, so use it for diffs, not for \"what's new\". Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / discovered_before / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / published_after / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"When the source published the entry (entries with no publish date are excluded; use top-level since to include them). Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / published_before / description
      Previous value: -"Relative window (\"7d\", \"36h\", \"45m\", \"2w\") or ISO date."New value: +"Relative window (\"7d\", \"36h\", \"45m\", \"2w\"), \"now\", or ISO date."
    • changedInput schema / properties / where / properties / source / properties / exclude / items / description
      Previous value: -"A source id (from any v2 response) or its exact title."New value: +"A source id (from any v2 response) or its title. Reads also accept a fragment that matches exactly one title."
    • changedInput schema / properties / where / properties / source / properties / include / items / description
      Previous value: -"A source id (from any v2 response) or its exact title."New value: +"A source id (from any v2 response) or its title. Reads also accept a fragment that matches exactly one title."
  2. Changed15 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / dry_run / description
      Previous value: -"Default true: the first call always previews blast radius and returns a commit_token."New value: +"Default true: preview affected records and return a commit_token. Explicit false applies immediately; prefer preview then commit_token for agent workflows."
    • changedInput schema / properties / op / description
      Previous value: -"Namespaced by noun: the noun fixes what `where` selects (sources.* select sources, entries.* select entries, collections.* select one collection)."New value: +"sources.* use where.source or where.collection, never entry filters. entries.* use the full where predicate. collections.rename/delete select one where.collection; collections.create uses set.name."
    • changedInput schema / properties / set / additionalProperties
      Previous value: -{}New value: +false
    • changedInput schema / properties / set / properties / collection / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / set / properties / collection / description
      Added value: +"Required for sources.move: destination collection id or name."
    • addedInput schema / properties / set / properties / name / description
      Added value: +"Required for collections.create and collections.rename: the collection name."
    • addedInput schema / properties / set / properties / title / description
      Added value: +"Required for sources.rename: the new source title."
    • changedInput schema / properties / where / description
      Previous value: -"Selection predicate shared by every feeds operation. All fields AND together; omit a field to not filter on it."New value: +"Entry selection predicate: fields AND together; omit a field to not filter on it. Source queries/mutations accept only collection and source; use query having for source-health filters."
    • changedInput schema / properties / where / properties / collection / items / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "maxLength": 100,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / where / properties / collection / minItems
      Added value: +1
    • changedInput schema / properties / where / properties / source / properties / exclude / items / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "maxLength": 500,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / where / properties / source / properties / exclude / minItems
      Added value: +1
    • changedInput schema / properties / where / properties / source / properties / include / items / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "default": 0,
-        "type": "string"
-      },
-      {
-        "maximum": 9007199254740991,
-        "minimum": 1,
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "maxLength": 500,
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / where / properties / source / properties / include / minItems
      Added value: +1
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

It explicitly states dry_run:true changes nothing and returns would_affect, sample, and commit_token, while dry_run:false applies immediately. It also discloses that commit_token is single-use and idempotent, consistent with the destructiveHint annotation and with no contradictions.

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?

The description is front-loaded and efficient, with examples and clear workflow guidance. The phrase 'Check partial and each outcome after committing' is vague and slightly disrupts an otherwise crisp structure.

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?

Given the output schema exists, the description appropriately focuses on workflow and selector constraints, covering dry-run behavior, commit semantics, and per-operation requirements. It could be more explicit about partial or per-item failure reporting, but enough is present for correct use.

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

Parameters5/5

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

All five parameters are covered in schema descriptions, including op-specific constraints such as sources.move needing set.collection and collections.rename/delete needing exactly one where.collection. The where descriptions clarify AND semantics and field-specific caveats like discovered_after versus published_after.

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?

The description clearly states that the tool previews and commits selector-based writes to sources, entries, or collections, and the op field enumerates concrete actions such as sources.move and collections.delete. It also distinguishes itself from manage_collections by directing direct collection CRUD elsewhere.

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

Usage Guidelines4/5

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

The description explains the preview/commit_token workflow, notes that dry_run:false applies immediately, and advises preferring preview then commit_token for agent workflows. It also points to manage_collections for direct CRUD, though it could mention when to use a read tool first to discover selectors.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All smry Product toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources