Skip to main content
Glama

getUploadLimits

Retrieve your Pinata account's upload limits, including the maximum files allowed per folder, so you can split larger directories before uploading.

Instructions

Get the upload limits of your Pinata account: folder_max_files, the most files one folder can hold (30,000 unless the account has its own limit). uploadFolder refuses a new folder of more files before sending any; upload such a directory as several folders.

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": "getUploadLimits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose genuinely useful behavior: the default value (30,000), the possibility of an account-specific limit, and how uploadFolder enforces it. However, it says nothing about authentication requirements, whether the call is cached or rate limited, or what the response shape looks like beyond the single named field.

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?

Two sentences, front-loaded with the core purpose and the returned field, with no filler or restatement of the tool name. The second sentence is slightly telegraphic ('uploadFolder refuses a new folder of more files before sending any'), which costs a little readability for its density.

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?

For a zero-parameter read tool with no output schema, this is essentially complete: it names the single returned value, gives its default, and explains the practical consequence for the sibling upload path. An agent has everything needed to decide to call it and to interpret the result.

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?

The tool takes zero parameters, so per the baseline this scores 4. The description correctly spends no words on parameters and instead explains the returned value, which is the more useful place to put detail here.

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 ('Get the upload limits of your Pinata account') and names the exact field returned (folder_max_files). It also anchors the tool against the sibling uploadFolder by explaining the relationship, so an agent can tell what this tool is for without opening anything else.

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?

Guidance is strong but implied rather than stated outright: by explaining that 'uploadFolder refuses a new folder of more files before sending any' and that oversized directories should be split into several folders, it makes clear when to consult the limit. It never explicitly says 'call this before uploading a large folder,' leaving the trigger for an agent to infer.

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