Skip to main content
Glama
Sign In
gpsem

gpsem

by puples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Modifier les paramètres du site

updateSiteSettings
Idempotent

Update site settings for a GPSEM site by specifying any optional fields like name, description, audience, or SEO parameters. Use this to adjust site configuration without resubmitting unchanged values.

Instructions

Modifier les paramètres du site — Champs de getSiteSettings, tous facultatifs. — (PATCH /sites/{siteId}/parametres)

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": {
      "siteId": "<siteId>",
      "body": "<body>"
    },
    "name": "updateSiteSettings"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesname, description, sector, brand_positioning, goal, site_type, audience, internal_links_per_page, min_words, index_test, index_tests_per_day, generate_images, flexible_content
siteIdYesID site encodé (hashid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds the valuable detail that all fields are optional, indicating partial updates are possible, and reveals the PATCH method. It does not contradict annotations and provides useful behavioral context (partial update semantics) beyond what annotations state.

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 description is exceptionally concise: a single sentence plus the endpoint. It front-loads the action, then adds the relationship to getSiteSettings, and finally the HTTP method. There is no filler or repetition, and every element contributes to the agent's understanding.

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?

For a tool with two parameters and a nested body, the description provides the essential context: it links the body fields to getSiteSettings and states they are optional, which guides the agent on what to send. The lack of return-value specification is a minor gap, but the overall guidance is adequate for correct invocation, especially given the reference to the GET tool for field details.

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?

Schema description coverage is 100% (both parameters have descriptions). The tool description reinforces that the body fields are from getSiteSettings and explicitly states 'tous facultatifs' (all optional), which is not evident from the schema alone. This adds meaningful semantic clarity about the body parameter's flexibility.

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 clearly states the action 'Modifier les paramètres du site' (modify site settings), identifies the resource (site settings), and references the associated GET tool (getSiteSettings) to define scope. It distinguishes from siblings like updateCompanyInfo or updatePage by explicitly naming the target as site settings and including the PATCH endpoint.

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?

The description effectively tells the agent that the body fields correspond to getSiteSettings and that all are optional, implying a fetch-then-modify workflow. It does not explicitly mention alternative tools or when not to use this one, but the reference to getSiteSettings provides clear contextual usage guidance beyond mere identification.

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