Skip to main content
Glama
Sign In
byline

byline

by indianic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Upload image

upload_image

Upload a local image to a site's media store and retrieve the hosted URL for embedding in blog posts.

Instructions

Upload a local image to a site's media store and return the hosted URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "path": "<path>"
    },
    "name": "upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
altNo
pathYesLocal path returned by generate_image
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It names the action and return value (hosted URL) but does not disclose side effects, error behavior, or prerequisites. The transparency is adequate but minimal.

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 a single, clear sentence with no redundant or extraneous information. It is appropriately sized for the tool's simplicity.

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?

For a simple tool with three parameters and no output schema, the description conveys the core functionality and return value. It could mention prerequisites like 'site must be existing' but is otherwise sufficiently complete.

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

Parameters2/5

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

Schema description coverage is only 33% (only 'path' is described). The description does not add meaning for 'site' or 'alt', leaving their roles ambiguous.

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 action (upload), the object (local image), the destination (site's media store), and the result (hosted URL). This distinguishes it from sibling tools like generate_image which creates an image.

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

Usage Guidelines3/5

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

The description implies usage: when you have a local image to host, upload it to a site. However, it does not explicitly mention alternatives, exclusions, or prerequisites such as the site needing to exist.

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

Deploy Server

Other Tools