---
ref: tool:g2/browse-product-buyer-intent
name: Browse buyer intent for a product
company: company:g2
workflows: [workflow:competitor-intent]
access: [mcp, api]
tags: [capability:track-intent, category:intent, has:api, has:mcp]
docs: https://data.g2.com/api/v2/docs/index.html
updated: 2026-09-27
---

# Browse buyer intent for a product

Returns the companies researching one of your products or its competitors on G2, ranked by intent score, with their activity and signal types.

Pass your product's identifier as `subject_product_id`. Rows are sorted by
`-company_intent_score` unless you set `sort`. Leave `day` out of
`dimensions` for one row per company, or add it for a daily series. Results
include activity on competitors in your categories: when `left_product_id`
differs from `subject_product_id`, the company was looking at the competitor
named in `left_product_name`. Needs the `buyer_intent.read` scope.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "g2": { "url": "https://mcp.g2.com/mcp" } } }
```

Call the MCP tool `browse_product_buyer_intent`.

Server URL: https://mcp.g2.com/mcp

### API (official)

- Base URL: https://data.g2.com
- Endpoint: `GET /api/v2/products/{subject_product_id}/buyer_intent`
- Auth: send the header `Authorization: Bearer $G2_API_KEY`
- Get a key: https://my.g2.com/developers
- Docs: https://data.g2.com/api/v2/docs/index.html

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.