[FEATURE] Docs: ApifyActorsTool example with a typed-input Actor
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Read the existing ApifyActorsTool documentation page and its apify/rag-web-browser example to follow the page’s structure. Add a short example for a jobs Actor with typed inputs, showing one direct call and one use with an agent; done when both usages and the typed fields are clear in the docs.
Written by the indexing model from the issue text.
Description
Feature Area
Documentation
Is your feature request related to a an existing bug? Please link it here.
NA
Describe the solution you'd like
The ApifyActorsTool page only shows apify/rag-web-browser, whose input is a query string. The useful part of the tool is that it builds its argument schema from the Actor's input schema, but nothing on the page shows an Actor with several typed fields. I'd add a second short example under the existing one: a jobs Actor with keyword, location, time window and a result cap, called directly once and then handed to an agent. Happy to open the PR if that fits.
Additional context
Drafted with an AI assistant, so per CONTRIBUTING this should carry the llm-generated label; I can't apply labels myself.
- Dominant language
- Python
- Stars
- 60.4k
- Forks
- 9k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 210
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from crewAIInc/crewAI
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
crewAIInc/crewAI#9200 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] Scrape tools reject the documented cookies mapping and drop cookies when the URL is passed at runtimePossibly taken @Luckyou-d claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[BUG] OpenAI-compatible embedding model alias breaks embedder constructionPossibly taken @gokay-ai claimed this 10 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
crewAIInc/crewAI#8761 · 1 comment ·
Maintainers usually reply within 1 day
-
[FEATURE] Add api_base_url to TavilySearchTool and TavilyExtractorToolPossibly taken @jayfeng7 claimed this 11 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
crewAIInc/crewAI#8635 · 1 comment ·
Maintainers usually reply within 1 day
All issues in crewAIInc/crewAI
Similar issues
-
[Bug] vllm-sr config migrate drops providers.models[].deploymentPossibly taken @Bevisy claimed this today. Openneeds-acceptance wg/developer-experience-ecosystem
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
vllm-project/semantic-router#5996 ·
Maintainers usually reply within 2 days
-
bugfix low-priority plugin:abstract plugin:leyline small-effort source:discussion
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
athola/claude-night-market#1132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
WeblateOrg/language-data#2773 ·
Maintainers usually reply within 1 day
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Niko1221/Strata#5553 · 2 comments ·
Maintainers usually reply within 4 days