Databricks ACTION
Query Vector Search Index Next Page
Fetch the next page of results from a previously executed Databricks Vector Search query, using the
next_page_token returned by a prior call. Run Query Vector Search Index first to get an initial page and its next_page_token, then pass that token here (and again on each subsequent call) to walk through all pages. Results are returned in groups of up to 1000, with a maximum of 10,000 total; an empty next_page_token in the response means there are no more pages. See the documentation.- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Databricks account once, then configure and run Query Vector Search Index Next Page 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: "databricks-query-vector-search-index-next-page",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
databricks: { authProvisionId: "apn_xxxxxxx" },
endpointName: "Endpoint Name",
indexName: "Index Name",
},
})
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": "databricks-query-vector-search-index-next-page",
"configured_props": {
"databricks": { "authProvisionId": "apn_xxxxxxx" },
"endpointName": "Endpoint Name",
"indexName": "Index Name"
}
}'// 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": "databricks",
},
},
},
)
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: "databricks-query-vector-search-index-next-page",
arguments: {
endpointName: "Endpoint Name",
indexName: "Index Name",
},
})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 |
|---|---|---|
endpointName Endpoint Name | string | The name of the vector search endpoint Required Dynamic |
indexName Index Name | string | The name of the vector search index Required Dynamic |
pageToken Page Token | string | The pagination token to fetch the next page of results. Use the next_page_token value returned by a prior Query Vector Search Index or Query Vector Search Index Next Page call (e.g. eyJpZCI6MTIzfQ==). Required |
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
- databricks-query-vector-search-index-next-page
- Version
- 0.0.2
- App
- Databricks
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗