Skip to main content
Glama

List website links

list_site_links
Read-onlyIdempotent

List real SaaS marketing websites as plain links: name and homepage URL only. Same filters as search_sites, up to 50 at a time. Use it when you want a batch of live sites to open and study yourself in a browser; this server never fetches them. Use search_sites or get_site for palettes, fonts, stacks and sections.

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

Input Schema

NameRequiredDescriptionDefault
fontNoFont family used on the site, e.g. "Inter".
colorNoHex colour; matches sites with a close colour in their palette, e.g. "#5e6ad2".
limitNoMaximum number of links to return, 1–50 (default 20).
queryNoFree text, e.g. "developer tools", "linear", "video editing".
stackNoTech stack of the marketing site, e.g. "Next.js", "Webflow", "Framer".
styleNoVisual style: "dark", "light", "colorful" or "minimal".
sectionNoOnly sites with this section captured, e.g. "pricing", "heroes", "faq", "footers".
categoryNoProduct category, e.g. "AI", "Engineering & Infrastructure". See list_filters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of links to return, 1–50 (default 20)."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: output is limited to name + URL, capped at 50, and the server never fetches the sites. It doesn't mention ordering or pagination, keeping it short of a 5.

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 tight sentences, front-loaded with the output shape, followed by the sibling pointer. Every sentence adds distinct information with no repetition.

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?

With no output schema, the description correctly compensates by stating exactly what is returned (name and homepage URL). Filters are fully documented in the schema; only minor details like result ordering are absent.

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 coverage is 100% with per-parameter descriptions and examples, so the schema carries the load. The description only adds that filtering mirrors search_sites and the 50-item cap, which is already in the schema's limit field — baseline 3 is appropriate.

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 real SaaS marketing websites as plain links') and precisely bounds the output ('name and homepage URL only'), which sharply separates it from search_sites and get_site that return richer data.

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?

Explicitly names the use case ('when you want a batch of live sites to open and study yourself in a browser') and routes the agent to alternatives ('Use search_sites or get_site for palettes, fonts, stacks and sections') with the condition that selects them.

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