Skip to main content
Glama

netlify_get_site

Read-onlyIdempotent

Fetches details for a single Netlify site by site ID using an access token, enabling targeted site inspection or management in automation workflows.

Instructions

Get a single Netlify site by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "access_token": "<access_token>"
    },
    "name": "netlify_get_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoNetlify site id (can be a saved default)
access_tokenYesNetlify personal access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the single-resource lookup shape and confirms identification by id; it says nothing about auth failures, not-found behavior, or default-site resolution hinted at in the schema.

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?

One short sentence, front-loaded with the verb and resource, with zero filler. Nothing could be profitably removed.

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?

A low-complexity single-record read with full schema coverage and rich annotations; the description is sufficient to call it correctly. Minor gaps (default-site behavior, not-found handling) are low-risk given the annotations.

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 both site_id and access_token documented, so the baseline is 3. 'By id' reinforces that site_id identifies the record, but the description does not clarify that site_id is technically optional in the required list despite being functionally necessary.

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?

States a specific verb and resource ('Get a single Netlify site') and scopes it to one item ('by id'), which implicitly contrasts with netlify_list_sites. It does not explicitly name the sibling, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

No guidance on when to use this versus netlify_list_sites or how to obtain a site_id first. The agent must infer the lookup-vs-list distinction from the names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools