Skip to main content
Glama

List my Siteiz sites

list_my_sites
Read-onlyIdempotent

Lists the sites in your Siteiz account with their latest AI readability score, open fixes and linked Search Console property. Needs a Siteiz Pro API key (Authorization: Bearer header).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the safety hints provided in annotations (readOnlyHint, destructiveHint), the description reveals critical operational context, notably the specific authentication method required (Siteiz Pro API key and Authorization: Bearer header). It also details the specific data returned, which is highly valuable for the AI agent.

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 two sentences are perfectly utilized. The first defines the content, and the second provides the necessary operational requirements, leading with the most important functional data.

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?

Given that this is a list-all tool with zero required parameters, it is exceptionally complete. All necessary contextual information, including required credentials and data points, is supplied in the description.

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?

Since there are zero input parameters, the baseline score of 4 is applied. The description does not need to clarify parameters, but it provides semantic context for the entire action by listing the metrics returned.

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?

The description is extremely clear, stating that the tool lists sites and provides three specific data points: AI readability score, open fixes, and linked Search Console property. This clearly defines the resource and its output.

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 implies usage by defining exactly what the tool gathers, but does not explicitly differentiate it from other sibling tools like 'get_search_performance' for specific comparison. However, it is clear enough for a list operation.

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