smry Product

manage collections (list/create/update/delete)

manage_collections

Destructive

list: Returns the same owner-scoped Collections shown in /feeds, including canonical filter state and revision. Required fields: none. Example: {"action":"list"} create: Creates the same named Collection used by the production /feeds UI. Required fields: name. Example: {"action":"create","name":"Research"} update: Membership is a complete replacement, matching the production Collection editor. Required fields: id. Example: {"action":"update","id":12,"name":"Engineering"} delete: Deletes a custom Collection and moves its inputs to Unsorted. Required fields: id. Example: {"action":"delete","id":12}

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No
`name`	No
`action`	Yes	"list": List Collections and their managed-feed filters · "create": Create a Collection · "update": Rename a Collection or replace its input membership · "delete": Delete a Collection
`source_ids`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / id / anyOf

Removed value: -[
-  {
-    "default": 0,
-    "type": "string"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": 1,
-    "type": "integer"
-  }
-]

addedInput schema / properties / id / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / id / minimum
```
Added value: +1
```
addedInput schema / properties / id / type
```
Added value: +"integer"
```

removedInput schema / properties / source_ids / items / anyOf

Removed value: -[
-  {
-    "default": 0,
-    "type": "string"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": 1,
-    "type": "integer"
-  }
-]

addedInput schema / properties / source_ids / items / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / source_ids / items / minimum
```
Added value: +1
```
addedInput schema / properties / source_ids / items / type
```
Added value: +"integer"
```

AddedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds concrete behavioral detail beyond that: update is a complete membership replacement and delete moves inputs to Unsorted. It also clarifies that list returns canonical filter state and revision. Missing auth, rate-limit, or idempotency details are not critical given the output schema and annotations.

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?

The description uses a tight action-keyed structure with a one-line semantic statement and one JSON example per action. Every sentence contributes a distinct constraint or behavioral fact, and there is no redundant filler or restatement of the schema.

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 an output schema present and destructive annotations already supplied, the description covers the essential context: action semantics, required fields, side effects, and production UI parity. The only notable omission is an explicit definition of source_ids, so an agent must infer its role from the membership replacement statement.

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?

The schema only describes the action parameter, so the description carries most of the semantic load. It adds conditional required fields (name for create, id for update/delete) and practical examples for each action. The source_ids parameter is only implied through 'Membership is a complete replacement' rather than explicitly documented, which is a small gap.

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?

Each action clause names a specific operation on a concrete resource: list returns owner-scoped Collections with canonical filter state and revision, create makes the same named Collection used by the /feeds UI, update replaces membership, delete removes a custom Collection and moves inputs to Unsorted. This is far more definitive than the title and clearly separates it from feed/library sibling tools.

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 gives clear per-action guidance through Required fields and examples tied to the production /feeds UI, which implies when to use this tool and what each action is for. It does not explicitly name alternatives or state when not to use it, but the collection-management context is unmistakable among the sibling tools.

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

All smry Product tools Inspect

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

Need Help?