HubSpot agent tool config describes the run you can prove
Write the agent tool's type, action description, inputs, and outputs as a contract you can demonstrate on every successful run.
Why this can grow a startup
The weakest agent listings treat configuration as metadata and the actual run as a separate concern. HubSpot treats them as one thing. `toolType` has to match the operation, `llmConfig.actionDescription` has to follow description guidance, and every configured output has to be returned in the promised format. That forces the product page, tool schema, and live behavior to agree. When they agree, the review process is faster and the buyer sees a workflow instead of a prompt-shaped guess.
Source-backed example
HubSpot says `GET_DATA`, `GENERATE`, and `TAKE_ACTION` should match the real job of the tool, and if the output config includes a `success_message` string the tool should return that property in the expected format on every run.
Source-reported evidence
Source: HubSpot Docs: Agent tool listing requirements · Browse HubSpot Docs: Agent tool listing requirements tactics
HubSpot requires tools to return the configured output fields in the expected format and to pass user acceptance tests by the Ecosystem Quality team.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Marketplaces, Product-led Growth, Engineering is relevant to tool schema, output contract, uat and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Product-led Growth, using evidence from HubSpot Docs: Agent tool listing requirements as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.
SOURCE HUB
More tactics from HubSpot Docs: Agent tool listing requirements
Explore related GrowthDex examples and evidence connected to HubSpot Docs: Agent tool listing requirements.
Open HubSpot Docs: Agent tool listing requirements source hub