Skip to main content
Glama

List Alibaba attachments

alibaba_list_attachments
Read-onlyIdempotent

Lists file attachments in an Alibaba conversation and returns attachment IDs, names, and sizes; requires read or read/write access.

Instructions

List file attachments in one Alibaba conversation. Requires read or read/write access. Returns ids, names, and sizes only. Remote addresses stay in the browser.

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": {
      "conversationId": "<conversationId>"
    },
    "name": "alibaba_list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
conversationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the bar is lower. The description still adds real value beyond them: it bounds the payload ('ids, names, and sizes only') and clarifies that remote addresses are not dereferenced server-side ('stay in the browser'), which sets expectations about what will be absent from results.

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?

Four short sentences, front-loaded with the action and scoped immediately by the conversation qualifier. Every sentence carries information; nothing is boilerplate, though the access-permission sentence could be folded into the first for tighter flow.

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?

For a two-parameter read tool with no output schema, the description says what comes back, which compensates for the missing output schema. The gaps are pagination and the undocumented limit parameter, which matter for a list operation capped at 100 results per call.

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 0%, so the description must carry parameter meaning and only partly does. The required conversationId is at least implied by 'in one Alibaba conversation', but the limit parameter (default 50, max 100) is never mentioned, and there is no guidance on pagination or how to enumerate beyond the cap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List file attachments in one Alibaba conversation'), which reads clearly as read-only enumeration and is distinguishable from the mutation siblings. It does not explicitly name how it differs from alibaba_download_attachment, but the 'returns ids, names, and sizes only' line draws the boundary implicitly.

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?

Gives a prerequisite ('Requires read or read/write access'), which is genuinely useful context for gating the call. It never says when to prefer this over alibaba_download_attachment, nor what to do when the conversation is unknown (e.g., call alibaba_list_conversations first), so usage is only implied.

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