Skip to main content
Glama

contentful_list_assets

Read-onlyIdempotent

List Contentful media assets for a specific space and environment, with an optional limit to control how many assets are returned.

Instructions

List Contentful media assets.

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": {
      "access_token": "<access_token>"
    },
    "name": "contentful_list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAssets to return (max 100, default 25)
space_idNoContentful space id (can be a saved default)
environmentNoEnvironment (default master)
access_tokenYesContentful Content Delivery API token

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no note that the limit defaults to 25 and caps at 100, and no indication of whether a space must be pre-configured as a saved default.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity is also the source of the missing context rather than a virtue in itself.

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?

For a four-parameter authenticated listing tool with no output schema, the description omits too much: required token/space configuration, pagination behavior, and what an asset record looks like are all left to the schema or guesswork. Annotations cover safety but not operational context.

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%, so limit, space_id, environment, and access_token are all documented in the schema itself. The description contributes no additional parameter semantics, which meets the baseline of 3 when the schema does the heavy lifting.

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 gives a specific verb and resource ("List Contentful media assets"), which is unambiguous on its own. It does not, however, distinguish itself from the sibling Contentful tools (contentful_list_entries, contentful_list_content_types), leaving the agent to infer that "assets" means media files rather than entries or content types.

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?

There is no guidance on when to use this versus contentful_list_entries or contentful_get_entry, and no mention of prerequisites such as needing a space_id or environment. The only usage signal is the tool name itself, which is not the description doing work.

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