Skip to main content
Glama
murphywuwu

easysociable-mcp

by murphywuwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List images

list_images
Read-onlyIdempotent

Browse owner-scoped media library images with an optional search query. Retrieve image IDs, CDN URLs, dimensions, and rights status for slot assignment.

Instructions

List owner-scoped image assets in the media library with optional search query q. Returns image IDs, CDN URLs, dimensions, and rights status for slot assignment. Call to browse media assets or discover imageId before slot binding. Alternatives: Use get_image to fetch full metadata for a specific imageId. Read-only query scoped to workspace owner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch term matching image name or provenance source.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNoArray of image asset records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "images": {
+      "description": "Array of image asset records.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changedv0.1.16
    • addedInput schema / properties / q / description
      Added value: +"Search term matching image name or provenance source."
  3. First observedv0.1.13

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the owner/workspace scoping and that results feed slot assignment. It does not mention pagination or result limits, which is a minor gap.

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-loads the core action and scope, then covers returns, usage, alternatives, and safety in order. Slightly redundant in mentioning slot context twice ('for slot assignment' and 'before slot binding'), but overall efficient.

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?

With an output schema present and rich annotations, the description needs only to cover scope, usage, and routing. It does all three, so an agent has everything required to select and invoke it correctly.

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 coverage is 100% and the single parameter q is already documented in the schema as a search term matching name or provenance source. The description only restates it as an 'optional search query q' without adding syntax or matching behavior, so the baseline 3 applies.

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 owner-scoped image assets in the media library') and names the scope ('scoped to workspace owner'). It clearly distinguishes itself from get_image, the sibling that handles single-image retrieval.

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?

Explicitly states when to use it ('browse media assets or discover imageId before slot binding') and names the alternative with its selecting condition ('Use get_image to fetch full metadata for a specific imageId'). Nothing is left to inference.

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