Skip to main content
Glama

List HelpCenter Images

helpcenter_list_images
Read-onlyIdempotent

List the images uploaded to the help center through the API (and so through this connector), newest first.

Read-only. Use it to find an image you uploaded earlier instead of uploading it again, or to reconcile after an interrupted run. Pictures added by hand in the article editor are a separate library and are not listed here.

Args:

  • limit (number, optional): items per page, 1-100 (default 100).

  • page (number, optional): page number (default 1).

  • checksum (string, optional): sha256 of a file's bytes, as hex — finds that exact file.

  • response_format ('markdown' | 'json'): default 'markdown'.

Returns: { total, count, page, per_page, total_pages, has_more, next, items } where each item is { id, url, filename, mime_type, size, checksum, alt_text, snippets, created_at }. alt_text is always empty on a read — alt text belongs to the in the article, not to the image.

Paging: every response carries next: { page, limit } — the exact arguments that fetch the first item it did not return — or null when nothing is left. Follow next, with the same filters, instead of computing page + 1 yourself. A response is capped at 25000 characters, in its text and in its structured data alike, and 5.0 MB in all: when a page does not fit, only its first items are returned (truncated: true, count says how many) and next points at the rest, usually with a smaller limit and a later page number. Requesting page + 1 with your original limit would skip them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "helpcenter_list_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1).
limitNoMaximum items to return per page (1-100, default 100).
site_idNoWhich help center to act on: an id from helpcenter_list_sites. Needed when this connection reaches more than one help center; omit it when it reaches one. Applies to this call only — pass it on every call of a task, and ask the user which help center they mean if their request does not say.
checksumNosha256 of the file's bytes, as hex. Finds an image by content, which is how to check whether an upload landed without listing everything.
response_formatNoOutput format: 'markdown' for a human-readable summary or 'json' for the full structured payload.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/no-destructive, and the description goes well beyond that: dual size caps (25000 characters in text and structured data, 5.0 MB overall), the truncation behavior and 'truncated: true' flag, why alt_text is always empty on a read, and the rule to follow 'next' rather than computing page + 1. This is the kind of operational detail annotations cannot express.

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?

Front-loaded with purpose, then a read-only note, then scope exclusion, then Args / Returns / Paging in clearly labelled blocks. The paging paragraph is long, but every clause (caps, truncation, why not page + 1) prevents a concrete failure, so it earns its space.

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?

No output schema exists, and the description fully compensates by spelling out the response envelope and item fields, including the non-obvious always-empty alt_text. Combined with paging and truncation rules, an agent has everything needed to call it and consume the result correctly.

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?

With 100% schema description coverage the baseline is 3, and the description still adds value by explaining intent for checksum ('finds that exact file') and the paging contract around page/limit. It omits site_id entirely from its Args list, which is the one parameter carrying a real routing decision (which help center to act on), though the schema documents it.

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?

States a specific verb and resource ('List the images uploaded to the help center through the API'), plus ordering ('newest first') and a scope boundary that separates it from the article editor's own image library. It is clearly distinguishable from siblings like helpcenter_get_image (single item) and helpcenter_upload_image.

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?

Gives concrete when-to-use cases ('find an image you uploaded earlier instead of uploading it again, or to reconcile after an interrupted run') and an explicit when-not ('Pictures added by hand in the article editor ... are not listed here'), which routes the agent away from a false expectation rather than leaving it to discover via empty results.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources