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

## Pin platforms

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

## Pin capabilities

```text
https://data.upscrape.com/mcp?capabilities=amazon.products.search,amazon.products.detail
```

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:

```text
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.

Do not pin hundreds of capabilities. The default search/describe flow exists to avoid flooding model context.