Clueso

Update or inspect article media

update_article_media

Update an article image/GIF (screenshot), or inspect its current state.

Provide one or more of zoom_factor, crop, shapes to change metadata.
Pass render=true (with no other updates) to fetch the current details without mutating.

To DELETE an article image/GIF: call update_article with markdown that omits the <SCREENSHOT id> reference. Unreferenced media is pruned server-side on save. There is no separate delete tool — the markdown IS the source of truth for what's present.

Input Schema

TableJSON Schema

Name	Required	Description
`crop`	No	Crop data: { position: [x,y], size: [w,h] } in fractional coords.
`render`	No	If true (and no other updates supplied), returns current details and a PNG preview without mutating.
`shapes`	No	Array of shape objects for annotations.
`project_id`	Yes	Project ID.
`zoom_factor`	No	Zoom magnification (1.0 = no zoom).
`screenshot_id`	Yes	Screenshot ID (from get_article).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
-  "type": "string"
-}

removedInput schema / properties / conversation_id

Removed value: -{
-  "description": "Echo 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.",
-  "type": "string"
-}

removedInput schema / properties / llm_model

Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "project_id",
-  "screenshot_id",
-  "context",
-  "llm_model"
-]New value: +[
+  "project_id",
+  "screenshot_id"
+]

Changed4 schema fields changedSep 22, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo 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.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "project_id",
-  "screenshot_id"
-]New value: +[
+  "project_id",
+  "screenshot_id",
+  "context",
+  "llm_model"
+]

Changed4 schema fields changedSep 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / crop / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / shapes / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedAug 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, which suggests the tool can mutate but is not destructive. The description adds crucial behavior: it can both mutate and inspect, and explicitly states that render=true performs a non-mutating fetch. It also reveals that deletion is not directly supported here, which is important behavioral context. No contradictions; just a minor gap on whether updates are reversible or any side effects.

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 well-structured with bullet points and a clear separation of update vs. inspect usage. It front-loads the primary purpose and then provides the deletion alternative. No redundancy; every sentence adds value. Slightly longer than minimal but justified given the dual functionality.

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 tool's moderate complexity (6 params, nested objects) and the absence of an output schema, the description fully compensates. It explains the update mode, the inspect mode, and the deletion path. It covers the key use cases and clarifies the source-of-truth for deletion, which is critical for correct usage. No missing critical information.

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?

Schema coverage is 100%, so each parameter is described. The description adds usage semantics (e.g., render=true with no other updates for inspection) but does not elaborate on shape structure or crop coordinate details beyond schema. Since schema is comprehensive, the baseline is 3; the description adds a little value by explaining how to combine parameters.

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 the dual purpose: update article media metadata (zoom, crop, shapes) or inspect current state via render=true. It distinguishes from the sibling update_article by noting that deletion is handled through markdown omission, not a dedicated delete tool. This distinguishes it from other media tools like add_article_media and generate_media.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: use render=true with no other updates for inspection, provide one or more of zoom_factor, crop, shapes for updates. It also explicitly details how to delete media (via update_article with markdown), preventing misuse and clarifying the tool's limits. This is exceptional guidance.

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

All Clueso 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.

Update or inspect article media

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources