flowsery

Official

by Flowsery

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Website Settings

get_metadata

Read-only

Retrieve a website's domain, timezone, currency, KPI goal, logo, and colors. Use it to obtain timezone and currency before running date-range reports, then pass those values to report tools.

Instructions

Get one website's settings: domain, timezone, currency, KPI goal name, logo, and color scheme. Read-only; nothing is changed. Call it after list_websites to learn the timezone and currency before running date-range reports, then pass that timezone to the report tools. With a workspace token pass websiteId or domain; with neither it returns the same website list as list_websites, so prefer list_websites for discovery. A website key needs no selector.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No	Website domain from list_websites (e.g. "example.com"). Alternative to websiteId with a workspace token.
`websiteId`	No	Website ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	Object with status and data: one entry with domain, timezone, currency, kpi, kpiColorScheme, and logo. Without a selector on a workspace token, the website list instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.1Sep 7, 2026

changedInput schema / properties / domain / description

Previous value: -"Website domain to query. Required when using a workspace token unless websiteId is provided."New value: +"Website domain from list_websites (e.g. \"example.com\"). Alternative to websiteId with a workspace token."

changedInput schema / properties / websiteId / description

Previous value: -"Website ID to query. Required when using a workspace token unless domain is provided."New value: +"Website ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key."

changedOutput schema / properties / result / description

Previous value: -"Website configuration including domain, timezone, currency, KPI goal, and color scheme."New value: +"Object with status and data: one entry with domain, timezone, currency, kpi, kpiColorScheme, and logo. Without a selector on a workspace token, the website list instead."

First observedv0.1.0Sep 7, 2026

TDQS

A4.8/5.0

Behavior4/5

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

The description reinforces the read-only nature and adds meaningful behavioral details beyond annotations, such as the fallback to returning the website list when no selector is given and the workspace-token versus website-key distinction. It does not cover error conditions or rate limits, but the core side-effect profile is well disclosed.

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 dense but every sentence adds distinct value: what is returned, read-only status, when to call it, how to pass parameters, and fallback behavior. It remains focused and free of fluff.

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 the output schema exists and parameters are fully described, the explanation is complete for an agent to decide when and how to invoke this tool. It covers caller context, selector semantics, and relationship to sibling tools, leaving no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers both parameters with descriptions, and the tool description adds crucial semantics: websiteId is required with a workspace token unless domain is given, while it is ignored with a website key. This goes well beyond the schema and clarifies selector logic.

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 tool retrieves settings for one website, enumerates the specific fields (domain, timezone, currency, KPI goal name, logo, color scheme), and explicitly contrasts it with list_websites for discovery. This distinguishes it well from sibling report and management tools.

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?

Provides explicit when-to-use guidance: call after list_websites to obtain timezone/currency before running date-range reports and pass that timezone to report tools. It also explains selector behavior for workspace tokens versus website keys and advises preferring list_websites when no selector is provided.

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