Skip to main content
Glama
AceDataCloud

AceDataCloud MCP Server

Official

acedatacloud_search_materials

Search marketing materials in the PublishMaterial catalog using keyword, language, channel, category, and tag filters. Optionally randomize results or include full content.

Instructions

Search marketing materials (ready-to-post copy) in the PublishMaterial catalog.

Combines server-side filters (language, channel) with client-side keyword
(title+content), category and tag matching, plus optional random selection.
Returns ``{count, returned, items}``; each item carries its quality_score,
channel_style and either a content preview or full content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoKeep materials whose tags overlap any of these.
langsNoFilter by one or more language codes, e.g. ['zh-cn', 'en'].
limitNoMax materials to return.
channelNoChannel UUID, or a name/title/domain substring (e.g. 'zhihu', 'CSDN').
keywordNoCase-insensitive substring matched against the material title AND content.
categoryNoCase-insensitive substring matched against the material category.
randomizeNoShuffle matches before returning (for random picks).
channel_idNoExplicit channel UUID (takes precedence over `channel`).
include_contentNoReturn full content instead of a short preview.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description provides useful behavioral details: server-side+client-side filtering, random selection, return format with quality_score and content preview/full. However, it omits pagination behavior, error handling, and potential performance impacts.

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?

Two sentences with a clear summary of functionality and return format. No unnecessary words, front-loads the purpose.

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

Completeness4/5

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

Given 9 optional parameters, high schema coverage, and an output schema, the description covers the main behavioral aspects. Lack of pagination details or error scenarios is minor gap.

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?

Schema coverage is 100% so baseline is 3. The description adds value by clarifying that 'channel' accepts name/title substring and 'keyword' is case-insensitive across title and content. This provides context beyond the schema's property descriptions.

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?

Clearly states it searches marketing materials (ready-to-post copy) in the PublishMaterial catalog. Differentiates from sibling tools like 'acedatacloud_search_docs' and 'acedatacloud_pick_random_materials' by specifying the resource type.

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

Usage Guidelines3/5

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

Describes the filter combination (server-side and client-side) but does not explicitly state when to use this tool over alternatives like 'acedatacloud_pick_random_materials' or 'acedatacloud_get_material'. No when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/AceDataCloudMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server