Skip to main content
Glama

list_ai_bots

Identify AI bots by user-agent, company, and description to manage access permissions in robots.txt files for web crawler control.

Instructions

List all known AI bots with their user-agents, companies, and descriptions. Useful for deciding which bots to block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `list_ai_bots` tool handler, which iterates over `ALL_BOTS` to format and return a list of known AI bots.
    server.tool(
      "list_ai_bots",
      "List all known AI bots with their user-agents, companies, and descriptions. Useful for deciding which bots to block.",
      {},
      async () => {
        const lines: string[] = [];
    
        lines.push("# Known AI & Search Engine Bots\n");
    
        const groups: Record<string, Bot[]> = {};
        for (const bot of ALL_BOTS) {
          const key = bot.type;
          if (!groups[key]) groups[key] = [];
          groups[key].push(bot);
        }
    
        const typeLabels: Record<string, string> = {
          "ai-crawler": "AI Crawlers (Training Data)",
          "ai-search": "AI Search Bots",
          "search-engine": "Search Engines",
          other: "Other Bots",
          social: "Social Bots",
        };
    
        for (const [type, bots] of Object.entries(groups)) {
          lines.push(`## ${typeLabels[type] || type}\n`);
          for (const bot of bots) {
            lines.push(`- **${bot.name}**`);
            lines.push(`  - User-Agent: \`${bot.userAgent}\``);
            lines.push(`  - Company: ${bot.company}`);
            lines.push(`  - ${bot.description}`);
            lines.push(
              `  - Default blocked: ${bot.defaultBlocked ? "Yes" : "No"}`
            );
            lines.push(`  - Docs: ${bot.docsUrl}`);
          }
          lines.push("");
        }
    
        return {
          content: [
            {
              type: "text" as const,
              text: lines.join("\n"),
            },
          ],
        };
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states this is a listing tool, implying it's likely read-only, but doesn't explicitly confirm safety (e.g., non-destructive), disclose rate limits, authentication needs, or behavioral traits like pagination or data freshness. The description adds minimal behavioral context beyond the basic purpose.

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?

The description is two concise sentences with zero waste: the first states the purpose and output details, the second provides usage context. It's front-loaded with the core action and efficiently structured.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains the purpose and usage but lacks details on behavioral aspects like data format, limitations, or error handling. For a read-only listing tool, this is minimally viable but could be more complete.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 clearly states the verb 'List' and resource 'all known AI bots' with specific attributes (user-agents, companies, descriptions). It distinguishes from siblings by focusing on comprehensive listing rather than analysis, checking, fetching, or generating. However, it doesn't explicitly differentiate from 'fetch_robots' which might be similar.

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 provides clear context for usage ('Useful for deciding which bots to block'), which implies this tool is for informational purposes to support blocking decisions. It doesn't specify when not to use it or name explicit alternatives among siblings, but the context is sufficiently clear for basic 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/sharozdawa/robotstxt-ai'

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