Skip to main content
Glama

cloudinary_list_resources

Read-onlyIdempotent

Lists Cloudinary media assets by resource type, public ID prefix, and result limit to inspect or select files for automation workflows.

Instructions

List Cloudinary media resources.

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": {
      "cloud_name": "<cloud_name>",
      "api_key": "<api_key>",
      "api_secret": "<api_secret>"
    },
    "name": "cloudinary_list_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResources to return (max 100, default 25)
prefixNoFilter by public_id prefix / folder
api_keyYesCloudinary API key
api_secretYesCloudinary API secret
cloud_nameYesCloudinary cloud name
resource_typeNoimage (default), video, or raw

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is fully covered by structured data. The description adds no behavioral context of its own: it does not mention that credentials are required per call, how pagination should be handled (cursor vs limit-only), or what the listing returns. With annotations carrying the safety profile, the description still earns little beyond the one-line restatement.

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?

It is a single front-loaded sentence with zero filler. Conciseness is genuinely good; the issue is under-specification, which is scored elsewhere, not verbosity.

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

Completeness2/5

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

This is a 6-parameter tool with 3 required credential fields and no output schema, so the description should explain the required authentication and how listing and pagination behave. It says nothing about either, leaving the agent to reconstruct the call shape from the schema alone.

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

Parameters3/5

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

Schema description coverage is 100%, with limit, prefix, resource_type, and the three required credential fields all documented in the schema itself. The description adds no syntax or semantics beyond the schema, so the baseline 3 applies rather than a higher score.

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?

The description states a specific verb and resource: list Cloudinary media resources. It is unambiguous about what the tool does. However, it does not differentiate this tool from its only Cloudinary sibling, cloudinary_get_usage, so the credit stops at clear purpose.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus cloudinary_get_usage, no mention of what the listing covers (account-wide vs folder-scoped), and no note about how prefix or resource_type narrowing should be applied. The agent must infer usage context entirely from the parameter schema.

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