Skip to main content
Glama

奇妙生产力 · Qimiao Productivity

by io.github.StarSailAI
OverviewDiscussionsAdmin

search_templates

Read-onlyIdempotent

免费检索实际模板。PPT可直接传完整需求（中英文）和可选constraints；服务端按多页视觉档案、背景明暗、用途、风格和排除条件返回最多五套推荐。结合evidence_previews展示封面与正文、fit和review的实际复核范围；不足五套不凑数，无匹配先调整需求。用户未选采用default_selection；报价将其template_id、template_version及存在时的template_internal_version放入input固定选择。检索不制作PPT、不生成图片、不收费。小红书封面支持完整自然语言要求，以及form、purpose、mood、color、brightness、photos、title、include_subjects、exclude_subjects等筛选；展示最多五张实际预览、推荐理由和素材提示，让用户选择后用template_id和template_version固定。不要把来源网站的使用量称为小红书爆款证据。其他工具仅在get_tool声明templates=true时调用。

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
tool_idYes
constraintsNo

Output Schema

NameRequiredDescriptionDefault
recoveryYes
next_stepYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / constraints / properties / exclude_subjects
      Added value: +{
+  "items": {
+    "enum": [
+      "person",
+      "product",
+      "animal",
+      "landscape",
+      "food",
+      "interface",
+      "illustration",
+      "none"
+    ],
+    "type": "string"
+  },
+  "maxItems": 8,
+  "type": "array"
+}
    • addedInput schema / properties / constraints / properties / form
      Added value: +{
+  "enum": [
+    "big-type",
+    "memo",
+    "notebook",
+    "illustration",
+    "photo-title",
+    "collage",
+    "dialog",
+    "comparison",
+    "magazine",
+    "product",
+    "infographic"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / constraints / properties / ignored
      Added value: +{
+  "items": {
+    "maxLength": 80,
+    "pattern": "^(?:color|form|purpose|mood|topic|brightness|photos|photo|subjects|required_subjects|exclude_color|exclude_mood)(?::[a-z][a-z-]{0,35})?$",
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
    • addedInput schema / properties / constraints / properties / include_subjects
      Added value: +{
+  "items": {
+    "enum": [
+      "person",
+      "product",
+      "animal",
+      "landscape",
+      "food",
+      "interface",
+      "illustration",
+      "none"
+    ],
+    "type": "string"
+  },
+  "maxItems": 8,
+  "type": "array"
+}
    • addedInput schema / properties / constraints / properties / mood
      Added value: +{
+  "enum": [
+    "professional",
+    "minimal",
+    "playful",
+    "gentle",
+    "retro",
+    "cute",
+    "bold",
+    "editorial"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / constraints / properties / photos
      Added value: +{
+  "enum": [
+    "none",
+    "available",
+    "any"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / constraints / properties / purpose / enum
      Previous value: -[
-  "report",
-  "technical",
-  "product",
-  "education",
-  "research",
-  "marketing",
-  "culture",
-  "event"
-]New value: +[
+  "report",
+  "technical",
+  "product",
+  "education",
+  "research",
+  "marketing",
+  "culture",
+  "event",
+  "tutorial",
+  "list",
+  "comparison",
+  "review",
+  "guide",
+  "experience",
+  "emotion",
+  "quote"
+]
    • addedInput schema / properties / constraints / properties / title
      Added value: +{
+  "maxLength": 300,
+  "type": "string"
+}
    • addedInput schema / properties / constraints / properties / topic
      Added value: +{
+  "enum": [
+    "technology",
+    "career",
+    "education",
+    "travel",
+    "food",
+    "beauty",
+    "home",
+    "parenting",
+    "health",
+    "fitness",
+    "pet",
+    "lifestyle",
+    "business",
+    "generic"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses important behavior: up to five recommendations, no padding when fewer match, preview/review scope, default selection handling, quote version pinning, and no charge. It also adds a caution against mislabeling source-site usage as Xiaohongshu viral evidence.

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

Conciseness3/5

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

The description is front-loaded with the core purpose and contains useful details, but it is a dense single block mixing PPT behavior, Xiaohongshu behavior, selection workflow, quoting, and warnings. Several clauses are operationally useful, but the lack of structure makes it harder to scan than necessary.

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

Completeness3/5

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

The tool is complex with nested constraints and an output schema, and the description covers behavioral context and selection workflow well. However, it leaves important parameter semantics undocumented despite 0% schema description coverage, so an agent still needs to infer required fields and pagination behavior.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It explains several constraint concepts such as form, purpose, mood, color, brightness, photos, title, and include/exclude subjects, but it never explains the required tool_id, offset, limit semantics, or many remaining constraint fields like industry, source_kind, background_scope, and exclusion lists.

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 opening states a specific verb and resource: free search for actual templates. It also clarifies that the tool returns recommendations rather than creating PPTs or generating images, but it does not explicitly distinguish itself from sibling search_tools beyond a gating note about get_tool.

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

Usage Guidelines4/5

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

The description gives clear usage context for PPT and Xiaohongshu cover scenarios, including how to pass natural-language requirements and optional constraints. It also states exclusions such as not making PPTs or images and not charging, but it does not name alternative tools or say explicitly when not to use this search.

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

All 奇妙生产力 · Qimiao Productivity toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources