Bridge Interactive Platform ACTION
Get Listings
Get MLS listings from a dataset. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Bridge Interactive Platform account once, then configure and run Get Listings from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "bridge_interactive_platform-get-listings",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
bridge_interactive_platform: { authProvisionId: "apn_xxxxxxx" },
dataset: "Dataset",
near: "Near",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "bridge_interactive_platform-get-listings",
"configured_props": {
"bridge_interactive_platform": { "authProvisionId": "apn_xxxxxxx" },
"dataset": "Dataset",
"near": "Near"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "bridge_interactive_platform",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "bridge_interactive_platform-get-listings",
arguments: {
dataset: "Dataset",
near: "Near",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
dataset Dataset | string | The dataset to use for the query Required |
near Near | string | Coord or location eg. near=-73.98,40.73 or near=San Diego Optional |
radius Radius | string | Search Radius in miles, km, or degrees (no units)s Optional |
box Box | string | Coordinates representing a box eg. box=-112.5,33.75,-123,39 Optional |
poly Poly | string | Minimum 3 pairs of coordinates representing a polygon eg. poly=-112.5,33.75,-123,39,-120,38 Optional |
geohash Geohash | string | Alphanumeric geohash eg. geohash=ezs42 Optional |
sortBy Sort By | string | Response field to sort query by Optional Dynamic |
order Order | string | Order of responses Optional |
fields Fields | string[] | Filters Response fields Optional Dynamic |
limit Limit | integer | Maximum number of responses Optional |
offset Offset | integer | Number of responses to skip Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- bridge_interactive_platform-get-listings
- Version
- 0.0.2
- App
- Bridge Interactive Platform
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗