Skip to main content
Glama
YGao2005

Scholar Feed MCP Server

Update Watch

update_watch

Update an existing watch's name, novelty floor, or filter criteria. Replacing criteria clears pending hits to prevent stale deliveries; use preview_watch to tune new criteria first.

Instructions

Update an existing watch in place — rename, change novelty_min, or RETARGET its structured filter criteria. MUTATES. Address by watch_id OR name. Changing criteria replaces the definition and clears the watch's pending hits (so stale matches don't deliver); the next daily eval repopulates. Structured watches rank by 'rising' (forecasted breakout impact) by default, and tighten with min_impact_pct for an anti-noise watch that surfaces only the breakout papers in your niche. Tune the new criteria with preview_watch first. Requires SF_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFind the watch by its current name. Provide this OR watch_id.
watch_idNoFind the watch by UUID. Provide this OR name.
new_nameNoRename the watch.
novelty_minNoNew novelty floor (0..1).
criteriaNoReplace the watch's filter (becomes kind='filter'). Clears pending hits.
recency_daysNoWindow for the new criteria.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoTrue when the operation succeeded.
messageNoHuman-readable summary of the outcome.
actionNoMachine label: saved | no_change | removed | liked | created | updated | deleted.
arxiv_idNo
collectionNoThe created/affected collection, when applicable.
watchNoThe created/affected watch, when applicable.
Behavior4/5

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

Mentions mutation, clearing pending hits on criteria change, ranking defaults, and min_impact_pct. Adds value beyond annotations which are minimal. No contradiction.

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?

Description is front-loaded with main purpose, then details. It is fairly long but every sentence adds necessary behavioral context. Slightly verbose but acceptable.

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

Completeness5/5

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

Given the complex nested schema and behavioral nuances, the description covers side effects, ranking logic, prerequisites, and tuning advice. Output schema exists, so return values are not needed.

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?

Schema coverage is 100%, baseline 3. Description adds extra meaning: explains side effects of changing criteria, ranking behavior, and tuning with preview_watch, enhancing understanding beyond 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?

The description clearly states 'Update an existing watch in place' with specific actions: rename, change novelty_min, or retarget filter. It distinguishes itself from sibling tools like create_watch and delete_watch.

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?

Provides context on addressing by watch_id or name, prerequisites (SF_API_KEY), and hints to use preview_watch first. Does not explicitly state when not to use or alternatives, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YGao2005/scholar-feed-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server