easysociable-mcp

List gradients

list_gradients

Read-onlyIdempotent

Search gradient presets by keyword or tag to discover styling options before building cards. Returns recipe summaries; follow up with a lookup for full CSS details.

Instructions

List or search platform gradient recipe summaries by keyword query or tag. Call to discover gradient presets before styling cards. Alternatives: Use get_gradient to retrieve full CSS declaration for a specific gradientId. Read-only platform catalog query.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Search term matching gradient name or tone.
`tag`	No	Style tag filter (e.g. vibrant, subtle, dark, pastel).
`limit`	No	Max items to return (prefer small limit for token budget).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`gradients`	No	Array of gradient summaries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.17Oct 5, 2026

addedInput schema / properties / limit / description

Added value: +"Max items to return (prefer small limit for token budget)."

addedInput schema / properties / q / description

Added value: +"Search term matching gradient name or tone."

addedInput schema / properties / tag / description

Added value: +"Style tag filter (e.g. vibrant, subtle, dark, pastel)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "gradients": {
+      "description": "Array of gradient summaries.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.13Oct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld=false, so 'Read-only platform catalog query' is largely redundant. The description does add real behavioral context beyond the annotations: results are summaries rather than full recipes, and full CSS requires the sibling get_gradient call. No permissions, pagination, or error behavior is described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero filler, front-loaded with the action and scope, then the use case, then the sibling routing. Every sentence carries distinct information.

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 read-only catalog list with full annotation coverage, a complete 100%-described schema, and an output schema, the description supplies everything the agent needs: what it returns (summaries), when to call it, and where to go for full detail.

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%, so q, tag, and limit are already fully documented in the schema. The description only restates the query/tag concepts and adds no syntax, matching rules, or limit guidance beyond what the schema provides, 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 ('list or search') plus resource ('platform gradient recipe summaries') and the narrowing fields (keyword query or tag). It also names the sibling get_gradient as a distinct operation, so an agent can separate the two without opening either schema.

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?

Gives an explicit trigger ('Call to discover gradient presets before styling cards') and an explicit alternative with its condition ('Use get_gradient to retrieve full CSS declaration for a specific gradientId'). Nothing about when-to-use 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.