Tool profiles and pinning

Tool pinning adds selected platforms or capabilities to a connection and exposes those capabilities as first-class tools with their own input schemas.

Pin platforms

https://data.upscrape.com/mcp?platforms=amazon,talabatmart

Pin capabilities

https://data.upscrape.com/mcp?capabilities=amazon.products.search,amazon.product.get

Pinned tools are added to the four default meta-tools. Visibility is still account-scoped: pinning cannot reveal a private capability the account is not allowed to use.

Tool names

Strict MCP clients reject dots in tool names. Upscrape maps dotted capability IDs to double underscores:

amazon.products.search  ->  amazon__products__search

The pinned tool accepts the capability's input object directly and waits for a result by default.

When pinning helps

• a client performs poorly with tool discovery;
• a workflow uses a small stable capability set;
• a client caches tool definitions and needs a deliberate, bounded list;
• direct first-class tool schemas are more useful than a meta-tool call.

Use profile=catalog only with a client configured for native tool search or enough tool capacity. Keep the compact or selected profile for clients that load all schemas upfront. Pinning does not restrict access through the generic execution tool; use key permissions or OAuth scopes for access control.