SavePinner MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_pinterest_urlA | Parse a Pinterest URL and return its kind, canonical URL, host, and type-specific identifiers. |
| normalize_pinterest_urlA | Convert a supported Pinterest URL to its canonical form and remove tracking parameters. |
| is_pinterest_urlA | Return whether a value is a supported Pinterest URL without making a network request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: one parses URLs, one normalizes them, and one validates them as Pinterest URLs. There is no overlap or ambiguity in their roles.
All tool names follow a consistent verb_object pattern: parse_pinterest_url, normalize_pinterest_url, is_pinterest_url. The pattern is predictable and uniform.
Three tools is exactly right for a focused URL utility server. Each tool addresses a specific need without clutter or redundancy.
The tool set covers the core operations for Pinterest URL handling: validation, parsing, and normalization. There are no obvious gaps for this narrow domain.