Slab ACTION
Search Posts
List or search posts in the Slab organization via the GraphQL
search endpoint. Leave Query empty to list all posts; provide a Query string to full-text search. This is the picker action agents should call to obtain post IDs for Get Posts, Update Post, Add Topic To Post, and Remove Topic From Post. Returns { posts, pageInfo } — posts is an array of post objects (e.g. {"id": "abc123", "title": "Engineering Onboarding Guide", "owner": {"id": "u1", "name": "Alice"}, "topics": [{"id": "abc12def", "name": "Engineering"}]}). Only forward pagination is supported: when pageInfo.hasNextPage is true, pass pageInfo.endCursor as After to retrieve the next page. Pass Fields (e.g. ["id","title","owner"]) to trim large fields like content from each post when only metadata is needed. See the documentation.- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Slab account once, then configure and run Search Posts 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: "slab-search-posts",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
slab: { authProvisionId: "apn_xxxxxxx" },
query: "Query",
first: 10,
},
})
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": "slab-search-posts",
"configured_props": {
"slab": { "authProvisionId": "apn_xxxxxxx" },
"query": "Query",
"first": 10
}
}'// 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": "slab",
},
},
},
)
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: "slab-search-posts",
arguments: {
query: "Query",
first: 10,
},
})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 |
|---|---|---|
query Query | string | Full-text search string. Leave empty ("") to list all posts in the organization. Optional |
first First | integer | Maximum number of posts to return per page (min 1), e.g. 20. Omit to use the API default page size. Optional |
after After | string | Cursor to start paginating forwards from. Pass the endCursor value from a prior response's pageInfo object (e.g. "cursor=abc123"). Leave blank to start from the beginning. Optional |
fields Fields | string[] | Optional list of top-level post fields to include in each result (e.g. ["id","title","owner"]). Omit to return the full post object for each result (default), including the potentially large content field. 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
- slab-search-posts
- Version
- 1.0.0
- App
- Slab
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗