Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

List Keywords

list_keywords
Read-only

List and search keywords with filtering, sorting, and pagination options.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional keyword name(s) to search for. Can be a single string or array of strings. Supports partial matching. Omit to list all keywords.
pageNoPage number for pagination (0-based indexing). Default is 0 for the first page.
sizeNoNumber of items per page (default: 25, recommended: 25-100).
sortNoSort criteria in format: field,direction. Options: id (creation order), avgMonthlySearches, lowerPageBid, higherPageBid, name, modifiedDate. Direction: desc (descending) or asc (ascending). Default: id,desc (newest first).id,desc
archivedNoFilter by archived status. Set to false to show active keywords (default), true to include archived keywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"Sort criteria in format: field,direction. Options: id (creation order), avgMonthlySearches, lowerPageBid, higherPageBid, name, modifiedDate. Direction: desc (descending) or asc (ascending). Default: id,desc (newest first). modifiedDate,desc lists keywords with no modifiedDate last."New value: +"Sort criteria in format: field,direction. Options: id (creation order), avgMonthlySearches, lowerPageBid, higherPageBid, name, modifiedDate. Direction: desc (descending) or asc (ascending). Default: id,desc (newest first)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / sort / default
      Previous value: -"modifiedDate,desc"New value: +"id,desc"
    • changedInput schema / properties / sort / description
      Previous value: -"Sort criteria in format: field,direction. Options: avgMonthlySearches, lowerPageBid, higherPageBid, name, modifiedDate. Direction: desc (descending) or asc (ascending). Default: modifiedDate,desc"New value: +"Sort criteria in format: field,direction. Options: id (creation order), avgMonthlySearches, lowerPageBid, higherPageBid, name, modifiedDate. Direction: desc (descending) or asc (ascending). Default: id,desc (newest first). modifiedDate,desc lists keywords with no modifiedDate last."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "avgMonthlySearches,desc",
-  "avgMonthlySearches,asc",
-  "lowerPageBid,desc",
-  "lowerPageBid,asc",
-  "higherPageBid,desc",
-  "higherPageBid,asc",
-  "name,desc",
-  "name,asc",
-  "modifiedDate,desc",
-  "modifiedDate,asc"
-]New value: +[
+  "id,desc",
+  "id,asc",
+  "avgMonthlySearches,desc",
+  "avgMonthlySearches,asc",
+  "lowerPageBid,desc",
+  "lowerPageBid,asc",
+  "higherPageBid,desc",
+  "higherPageBid,asc",
+  "name,desc",
+  "name,asc",
+  "modifiedDate,desc",
+  "modifiedDate,asc"
+]
  3. First observed

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, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — it does not mention the important default behavior (archived=false returns only active keywords) or the default sort (id,desc = newest first), both of which meaningfully change results.

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?

One clean, front-loaded sentence with no filler. It is efficiently sized, though the brevity comes at the cost of substance rather than being tight and informative.

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?

Given full schema coverage, rich annotations, and no output schema, the definition is just barely sufficient to invoke the tool correctly. It omits any mention of what is searched by name, the archived-inclusion default, and result shape, which for a list tool with a hidden archived filter is a real gap.

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 all five parameters (name, page, size, sort, archived) are fully documented in the schema including partial matching, array aggregation, and defaults. The description contributes no additional parameter meaning, so baseline 3 applies.

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?

States a specific verb and resource ('List and search keywords') plus the supported capabilities (filtering, sorting, pagination), so an agent knows exactly what the tool returns. It does not differentiate from near-siblings like list_negative_keywords_list, list_experiment_keywords, or list_search_terms, so the agent must infer that this covers the positive keyword library only.

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?

No when-to-use or when-not-to-use guidance and no named alternatives. The description never clarifies the relationship to create_keywords, list_negative_keywords_list, or list_experiment_keywords, leaving the agent to guess which listing tool matches its intent.

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

All Metadata MCP Connector 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