Skip to main content
Glama

Clueso

by io.clueso
OverviewDiscussionsAdmin

Add article media (image or GIF)

add_article_media

Add a screenshot or GIF to the article. Returns a screenshot_id to place in the article via update_article using <SCREENSHOT screenshot_id>.

  • kind="image": pass timestamp to capture a frame from the project's base video, OR pass mcp_upload_id (from the upload tool) to attach an uploaded image. One of the two is required.

  • kind="gif": pass timestamp (start) and duration (seconds). Captures a short GIF clip from the base video. Requires the project to have a video clip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes'image' or 'gif'.
durationNokind='gif' only: GIF duration in seconds.
timestampNokind='image': capture frame at this timestamp (seconds). kind='gif': GIF start time.
project_idYesProject ID.
mcp_upload_idNokind='image' only: attach an uploaded image (mcp_upload_id from the upload tool) instead of capturing from video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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: -[
-  "kind",
-  "project_id",
-  "context",
-  "llm_model"
-]New value: +[
+  "kind",
+  "project_id"
+]
  2. Changed4 schema fields changed
    • 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: -[
-  "kind",
-  "project_id"
-]New value: +[
+  "kind",
+  "project_id",
+  "context",
+  "llm_model"
+]
  3. Changed2 schema fields changed
    • 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
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses the mutating 'add' behavior, the capture/attach mechanics, the GIF video-clip prerequisite, and the returned screenshot_id, all of which add context beyond the annotations. It does not state whether timestamp and mcp_upload_id are mutually exclusive or what error occurs on invalid combinations, but annotations already cover the non-destructive, non-read-only profile.

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 is compact and front-loaded: purpose and output usage appear first, followed by tight bullets for each kind. Every sentence contributes necessary information, with no filler or repetition of schema details.

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?

The description covers both modes, required parameter combinations, the video prerequisite for GIFs, the return contract, and downstream integration with update_article. Minor gaps remain: it does not explicitly say whether adopting timestamp for an image also requires a video clip, and it does not address exclusivity of timestamp versus mcp_upload_id or error behavior.

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?

Although the schema describes each parameter in isolation, the description adds essential conditional semantics: kind=image requires one of timestamp or mcp_upload_id, while kind=gif requires timestamp plus duration alert. It also explains where mcp_upload_id comes from and what the successful result is, enabling correct parameter selection beyond 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?

The description opens with a specific verb-resource pair: "Add a screenshot or GIF to the article." It further clarifies the artifact returned (a screenshot_id used in update_article), which distinguishes this add operation from related siblings like update_article_media and upload_file.

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

Usage Guidelines2/5

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

The description provides no guidance on when to choose this tool versus alternatives such as update_article_media, add_audio, add_elements, or generate_media. The only usage conditions are internal to the tool (image vs. GIF modes), not tool-selection criteria; no when-not-to-use or alternative routing is given.

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

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