Skip to main content
Glama

List Connected Websites

list_websites
Read-onlyIdempotent

List the websites the user can query in LuBot.

Returns each site's id and name. Use this when the user asks about their website traffic, and to find the site_id that website_summary needs.

Without sign-in it returns LuBot's public demo site (lubobali.com); signed in, it returns the user's own sites. Signed-in users who haven't connected a site yet see the demo site, clearly labeled.

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_websites"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
websitesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"`list_websites` structured result (MARKET-17 S6-4 outputSchema).\n\nSame JSON as before: {\"websites\": [...]}."New value: +"The websites the user can see traffic for."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "WebsiteMeta": {
      +      "additionalProperties": false,
      +      "description": "A website project the caller can query traffic for.",
      +      "properties": {
      +        "display_name": {
      +          "title": "Display Name",
      +          "type": "string"
      +        },
      +        "is_demo": {
      +          "title": "Is Demo",
      +          "type": "boolean"
      +        },
      +        "site_id": {
      +          "maxLength": 64,
      +          "minLength": 1,
      +          "title": "Site Id",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "site_id",
      +        "display_name",
      +        "is_demo"
      +      ],
      +      "title": "WebsiteMeta",
      +      "type": "object"
      +    }
      +  },
      +  "additionalProperties": false,
      +  "description": "`list_websites` structured result (MARKET-17 S6-4 outputSchema).\n\nSame JSON as before: {\"websites\": [...]}.",
      +  "properties": {
      +    "websites": {
      +      "items": {
      +        "$ref": "#/$defs/WebsiteMeta"
      +      },
      +      "title": "Websites",
      +      "type": "array"
      +    }
      +  },
      +  "title": "WebsiteList",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds behavior those annotations cannot express: results vary by auth state, unauthenticated calls return the public demo site (lubobali.com), and signed-in users with no connected site see a clearly labeled demo fallback. That is genuinely useful context beyond the structured fields, with only return ordering or empty-state detail left out.

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?

Front-loaded with purpose and return shape, then the routing hint, then the auth-state behavior. Every sentence carries information; the auth paragraph is slightly longer than strictly needed but no sentence is filler.

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

Completeness5/5

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

With an output schema present, the description need not document return values, yet it still summarizes the id/name payload. Combined with the auth-state behavior, an agent has everything needed to call this zero-parameter tool and interpret the result correctly in both signed-in and anonymous cases.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly does not invent parameter guidance, instead spending its space on result semantics.

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?

States a specific verb and resource ('List the websites the user can query') and immediately names what it returns (each site's id and name). It also distinguishes itself from website_summary by naming the downstream consumer of the site_id, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the user asks about their website traffic') and an explicit downstream use ('to find the site_id that website_summary needs'). The alternative path is named rather than implied, so the routing decision between listing and summarizing is unambiguous.

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