Skip to main content
Glama

Social Media Agency Directory

List services

list_services
Read-onlyIdempotent

Service categories (for example Social Media Management, Paid Social Advertising, Influencer Marketing) with agency counts and directory URLs. Use the slug as the service filter of search_agencies. "Full-Service Digital" is a broad category.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
servicesYes
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely behavioral note — that 'Full-Service Digital' is a broad category — but its other content (counts, URLs) largely restates what the output schema already provides.

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, front-loaded sentences: what is returned, how to use it, and one caveat. There is no filler, and the caveat is placed last where it belongs after the primary action guidance.

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?

A zero-parameter list tool with full annotation coverage and an output schema needs little description, and this one still covers content, downstream usage, and one gotcha. Nothing required to call it is missing; the only soft gap is the absence of an explicit statement of how it differs from the other directory-browsing tools.

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?

With zero input parameters the baseline is 4, and the description goes further by explaining the meaning of the 'slug' value this tool emits and where to pass it (the service filter of search_agencies). That is output-value semantics rather than parameter semantics, so it does not push higher.

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 description names the resource concretely ('Service categories') and enumerates representative values (Social Media Management, Paid Social Advertising, Influencer Marketing) plus what each entry carries (agency counts, directory URLs). It is unambiguous about what the tool does, though it never explicitly contrasts itself with siblings like list_locations or directory_stats; the verb is only implied by the name.

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?

It gives concrete downstream guidance: 'Use the slug as the service filter of search_agencies', which tells the agent how this tool feeds the search workflow. It also flags that 'Full-Service Digital' is a broad category, warning against over-narrow interpretation. No when-not-to-use case is stated, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources