pinterest_auth_status
Check current Pinterest authentication status to confirm valid session and access permissions.
Instructions
Check current Pinterest authentication status.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Check current Pinterest authentication status to confirm valid session and access permissions.
Check current Pinterest authentication status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state that the tool is read-only, idempotent, safe, or any other behavioral traits. An agent cannot infer side effects or safety from 'Check status' alone.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the purpose. Every word is meaningful with no redundancy or filler, making it highly efficient for an AI agent to process.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the zero-parameter input and lack of output schema, the description is minimally complete. It communicates the tool's purpose but omits details about the return value (e.g., format, possible values), which could be important for an agent to use the result effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and the schema coverage is 100%, so the baseline score is 4. The description adds no parameter information, but none is needed. The tool is straightforward with no input requirements.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Check' and the resource 'Pinterest authentication status', making the tool's purpose immediately obvious. It distinguishes from sibling tools like 'pinterest_auth' by indicating this is a status query rather than an authentication action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as 'pinterest_auth'. The description does not include any context for when a status check is appropriate or any prerequisites or side effects.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/artyomredko-collab/sapyx-mcpclone'
If you have feedback or need assistance with the MCP directory API, please join our Discord server