Skip to main content
Glama
ThalesGroup

Imperva Cloud WAF MCP Server

Official
by ThalesGroup

get_sites_details_of_a_given_account_tool

Retrieve site details for an account, filtering by site ID, name, or sub-account ID. Returns empty list if site doesn't exist.

Instructions

Fetches the list of sites for a given account. To get a single site details provide the site Id or the site name. Use the most effective filter according to the context, for example, if you have the site ID use it; if you have the site name use it; If you get an empty list, it means that the site does not exist, or you do not have access to it, avoid getting all sites and filter on your side. Terminology: The site name is not always the domain name, to get the list of domains use the domains_get_domains_of_specific_site_tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesUnique identifier of the sub-account, if the account in context is the main account associated to the used API_ID this field MUST be empty (Optional)
site_idsNolist of external sites IDs, only sites with those IDs will retrieve, if exists (Optional)
namesNolist of sites names, only sites with those names will retrieve, if exists. (Optional)
sub_account_idsNolist of subaccount IDs, only sites under the matching subaccounts will retrieve, if exists. (Optional)
page_numNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It explains empty list meaning and advises against fetching all sites. However, it omits details on pagination (page_num, page_size), authentication requirements, rate limits, or error cases, leaving gaps in understanding.

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?

The description is short and front-loaded with purpose, but the phrase 'To get a single site details provide the site Id or the site name' is slightly wordy. Overall, no excessive information.

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 has 6 parameters and an output schema, the description covers essential filtering guidance and result interpretation. However, it lacks explanation of pagination parameters and does not address error handling or access prerequisites, leaving the agent slightly underinformed.

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 description adds value beyond the input schema by advising to use site ID or name for single details and warning against pulling all data. With 67% schema coverage, it compensates for partially documented parameters (page_num, page_size lack descriptions) but could elaborate more on sub_account_ids.

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 tool fetches a list of sites for a given account, and explains how to get single site details via ID or name. However, it does not explicitly differentiate from sibling tools, which are about domains, policies, and rules, so clarity is slightly diminished.

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?

Provides specific guidance on using filters effectively (e.g., use site ID if available) and interprets empty results. It mentions a sibling tool for domains but lacks explicit when-not-to-use scenarios or alternatives for filtering.

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/ThalesGroup/imperva-cloud-WAF-MCP-server'

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