Skip to main content
Glama
Sign In
Aktar

Aktar

Official
by getaktar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Show an upload's thumbnail

get_thumbnail
Read-only

Retrieve a small preview image for an uploaded photo, video, PDF, or document using its upload ID, so you can identify the file without downloading it.

Instructions

Get a small preview image of an upload from search_uploads (photos, videos, PDFs, documents...), to see what a file looks like without downloading it.

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": {
      "id": "<id>"
    },
    "name": "get_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe upload's ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description needn't repeat it. The description adds that the result is a "small preview image" rather than the full file, which is useful, but it never says how the image is delivered (raw image content, URL, base64) or whether resolution is capped — the main behavioral unknown for a thumbnail tool.

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?

One sentence, front-loaded with the verb and resource, with the purpose clause trailing it. The parenthetical file-type list is short and clarifies scope rather than padding.

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

Completeness3/5

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

There is no output schema and no annotations about return values, so the description bears the burden of describing the response and only partly does so ("small preview image"). It is adequate for a trivial single-parameter read, but the delivery format of the image remains an open question an agent must discover at call time.

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%, so the baseline is 3, and the description earns an increment by telling the agent where the id comes from (an upload returned by search_uploads). That provenance is real meaning beyond "The upload's ID" in the schema, though no format or validity constraints are added.

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 names a specific verb and resource ("Get a small preview image of an upload") and scopes it to the file types returned by search_uploads. An agent can immediately tell this apart from upload_file, create_temporary_link, or search_uploads without opening any schema.

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?

"to see what a file looks like without downloading it" gives a clear use condition and implicitly names the alternative (downloading the file). It does not state explicit exclusions or failure conditions, but the selection context is unambiguous for a one-parameter read tool.

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